.Net HTTP implementation bug?

  • Thread starter Thread starter Morgan Cheng
  • Start date Start date
M

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)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

HTTP implementatin bug? 1
Queer Problem 1
Transfer-Encoding chunked and WCF 1
IIS 7.0 and Windows Integrated Authentication? 1
Socket Programming Question 3
using httpwebresponse asynchronously - chunked response? 1
Q: HttpWebResponse Transfer-Encoding chunked - how to read trailers? 4
Why IE refuse to cache redirected image? 1

Back
Top