HTTP:collect 4MB limit bug>?

Hi Deb,

 

 

Thanks again for the quick response. I think there are cases when the content-length header is missing even when not chunking:

 

 

http://blogs.msdn.com/david.wang/archive/2006/02/28/Why-IIS6-can-send-invalid-HTTP-Responses.aspx

 

 

I don't know common this is, but seems to occur in real field situations. In those cases, I am assuming that the response could hang?

 

 

Thanks for the tip on TCP::notify. The docs indicate that the USER_RESPONSE event may wait until the data is sent - does it wait until all content is sent or just what has been released? In other words, does each call to TCP::notify result in a USER_RESPONSE event? If I call TCP::notify for each of the collect/release iteration, would it fire multiple times or just one final time?

 

 

Thanks again!

 

 

//Joe