> I thought HttpClient was a client for the _real-world_ HTTP-Servers, just as > the HTTP Clients of modern web browsers are/should be (I guess that's why > there is a switch to enable/disable "strict" mode in HttpClient).
If those so called real world servers do silly stuff, the fix should be applied where it is due > However, it may not even be a bug on the server side to generate output with > no end at all. What makes you think so? > But for now, it _will_ loop endlessly when > a) ChunkedInputStream close() or exhaustInputStream is called I agree that ChunkedInputStream#close() can be made more robust. I'll try to provide a patch by the end of the weekend. > b) getResponseBody() or getResponseBodyAsString() are called. Still disagree here. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
