Am Freitag, 10. Oktober 2003 18:02 schrieb Kalnichevski, Oleg: > > I can easily provide test cases which will cause HttpClient to eat up all > > available memory throwing an OutOfMemoryError because of reading and > > reading from a never ending HTTP Response. > > > > I would regard this behaviour as a bug. > > Sure. The bug in the software on the server side. And the fix should be > applied where it is due. > > Oleg
Sorry, I can't follow your argument. 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). However, it may not even be a bug on the server side to generate output with no end at all. And it would be no kind of problem if HttpClient would handle endless streams in better way. But for now, it _will_ loop endlessly when a) ChunkedInputStream close() or exhaustInputStream is called b) getResponseBody() or getResponseBodyAsString() are called. So, can you provide a bugfix for that, at least for non-strict mode, please? It would help a lot. Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
