HTTP implementatin bug?

[Morgan Cheng]

If a web server HTTP response is in chunked encoding, CLR client
invocation on HttpWebResponse.Close will not return until the whole
page is downloaded. If the page is huge, it looks the thread is stuck
in HttpWebResponse.Close. An example URL is http://wx.msn.com.

This might be a bug for CLR. I tried both 1.1 and 2.0.
With the help of network sniffer, I found that CLR doesn't have RESET
flag on invocation of HttpWebResponse.Close if the server http
response is in Chunked encoding (i.e. there is "TRANSFER-ENCODING:
chunked" in http header)

[Joerg Jooss]

Thus wrote Morgan,

If a web server HTTP response is in chunked encoding, CLR client
invocation on HttpWebResponse.Close will not return until the whole
page is downloaded. If the page is huge, it looks the thread is stuck
in HttpWebResponse.Close. An example URL is http://wx.msn.com.

Try closing the response stream instead.

This might be a bug for CLR. I tried both 1.1 and 2.0.
With the help of network sniffer, I found that CLR doesn't have RESET
flag on invocation of HttpWebResponse.Close if the server http
response is in Chunked encoding (i.e. there is "TRANSFER-ENCODING:
chunked" in http header)

I can't even access that site without crashing my browsers (both Firefox
2 and IE 7). A System.Net based client simply returns an empty response.
--
Joerg Jooss
ne********@joergjooss.de