DO NOT REPLY [Bug 23708] - DefaultHttpParamsFactory violates applet sandbox

2003-10-11 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Proposal: Configurable HTTP Response length limit

2003-10-11 Thread Christian Kohlschuetter
Am Samstag, 11. Oktober 2003 17:56 schrieb Michael Becke: > I agree with Oleg here. The real problem is the inability to terminate > a request and force close a connection. Having this functionality would > help in this case as well as many others. > > Mike I also agree that we need such functi

DO NOT REPLY [Bug 23708] - DefaultHttpParamsFactory violates applet sandbox

2003-10-11 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 23708] - DefaultHttpParamsFactory violates applet sandbox

2003-10-11 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Proposal: Configurable HTTP Response length limit

2003-10-11 Thread Michael Becke
I agree with Oleg here. The real problem is the inability to terminate a request and force close a connection. Having this functionality would help in this case as well as many others. Mike Oleg Kalnichevski wrote: I think the shortest example to demonstrate HTTPClient looping endlessly is

Re: Proposal: Configurable HTTP Response length limit

2003-10-11 Thread Oleg Kalnichevski
> I think the shortest example to demonstrate HTTPClient looping endlessly is > pointing to a chargen-Service: > > Enable chargen in inetd an try to access http://localhost:19/ > > It really does not matter from which side (server/client/user) the problem > arises, but it is HttpClient's job to

Re: Proposal: Configurable HTTP Response length limit

2003-10-11 Thread Christian Kohlschuetter
Here is the new patch (attached to this mail). Index: org/apache/commons/httpclient/AutoCloseInputStream.java === RCS file: /home/cvspublic/jakarta-commons/httpclient/src/java/org/apache/commons/httpclient/AutoCloseInputStream.java,v r

Re: Proposal: Configurable HTTP Response length limit

2003-10-11 Thread Christian Kohlschuetter
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

Re: Proposal: Configurable HTTP Response length limit

2003-10-11 Thread Christian Kohlschuetter
Am Freitag, 10. Oktober 2003 18:56 schrieb Eric Johnson: > (...) If we took > your suggestion and simply stopped reading the stream sent by the > server, when processing the _next_ request on the same socket, we'd run > into lots of problems. Eric, I think this is the problem of my workaround, wh