Re: DO NOT REPLY [Bug 24352] - NLTM Proxy and basic host authorization

2003-11-18 Thread Ortwin Glück
Michael Becke wrote: Odi, Eric, I think a combination of these techniques would be great. One level to handle the socket management(as Odi outlined) and another to handle the content creation/validation (Eric's idea). These two methods in tandem should be sufficient to mimic any combination

Re: Does HttpClient decompress compressed HTTP transfers?

2003-11-18 Thread Sven Köhler
It'd be rather easy to wrap the streams in a DeflaterOutputStream or an InflaterInputStream. Of course, due to limitations in Java's deflate compression, one must extend DeflaterOutputStream to allow true stream deflation. The problem with the current implementation is that there is no way

Re: DO NOT REPLY [Bug 24560] - HttpClient loops endlessly while trying to retrieve status line

2003-11-18 Thread Christian Kohlschtter
On Monday 17 November 2003 21:05, Oleg Kalnichevski wrote: I have not found any mentioning of unexpected content in the RFC, so this is another reason why I would be a bit cautious about throwing a protocol exception. It would suffice to spit out a warning, drop the connection and move on.

Re: DO NOT REPLY [Bug 24352] - NLTM Proxy and basic host authorization

2003-11-18 Thread Christian Kohlschütter
On Monday 17 November 2003 20:33, Oleg Kalnichevski wrote: [Disregard my previous post. I responded to a wrong message by mistake] Odi, That would be REALLY cool! A simple authenticating proxy (or a proxy that could effectively 'fake' popular authentication schemes) would be a very much

Re: DO NOT REPLY [Bug 24352] - NLTM Proxy and basic host authorization

2003-11-18 Thread Ortwin Glück
Christian Kohlschütter wrote: Please have a look at the latest version (see http://nagoya.apache.org/bugzilla/showattachment.cgi?attach_id=9093 ). It is more abstract than the BadHTTPServer example for Bug 24560 and truly test independent. What sort of file is that? It seems binary...

RE: DO NOT REPLY [Bug 24560] - HttpClient loops endlessly while trying to retrieve status line

2003-11-18 Thread Kalnichevski, Oleg
Christian, Feel free to make changes to the patch that you deem necessary. Once you think it is ready, I suggest we once again ask all the interested parties to raise their objections and express concerns. If there's no significant opposition to the final revision of the patch, and it is OKed

Re: DO NOT REPLY [Bug 24352] - NLTM Proxy and basic host authorization

2003-11-18 Thread Christian Kohlschütter
On Tuesday 18 November 2003 11:26, Ortwin Glück wrote: Christian Kohlschütter wrote: Please have a look at the latest version (see http://nagoya.apache.org/bugzilla/showattachment.cgi?attach_id=9093 ). It is more abstract than the BadHTTPServer example for Bug 24560 and truly test

Re: DO NOT REPLY [Bug 24352] - NLTM Proxy and basic host authorization

2003-11-18 Thread Ortwin Glück
Christian Kohlschütter wrote: On Tuesday 18 November 2003 11:26, Ortwin Glück wrote: Christian Kohlschütter wrote: Please have a look at the latest version (see http://nagoya.apache.org/bugzilla/showattachment.cgi?attach_id=9093 ). It is more abstract than the BadHTTPServer example for Bug

Re: DO NOT REPLY [Bug 24352] - NLTM Proxy and basic host authorization

2003-11-18 Thread Christian Kohlschütter
On Tuesday 18 November 2003 11:53, Ortwin Glück wrote: Christian Kohlschütter wrote: On Tuesday 18 November 2003 11:26, Ortwin Glück wrote: Christian Kohlschütter wrote: Please have a look at the latest version (see http://nagoya.apache.org/bugzilla/showattachment.cgi?attach_id=9093 ).

Re: DO NOT REPLY [Bug 24352] - NLTM Proxy and basic host authorization

2003-11-18 Thread Ortwin Glück
Christian Kohlschütter wrote: I own the copyright for this code and I am willing to contribute / publish it under the conditions of the Apache License. Thanks a lot! I will check it in on the 2.0 branch since it is related to a 2.0 bug. As soon as it is ready we can promote it to CVS HEAD.

read timeout with persistent connection

2003-11-18 Thread Matthew McGowan
Greetings, With HttpClient, I'm using the MultiThreadedHttpConnectionManager, with all timeout values set to 30s, and I'm seeing a problem against a server that discards unused connections after several minutes. It seems the connection close isn't detected by the HttpConnection.isStale() method,

Re: read timeout with persistent connection

2003-11-18 Thread Ortwin Glück
There is an option to disable stale checking. Matthew McGowan wrote: Any ideas how I go about fixing this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 24504] - Cannot create a document that has accent characters (Latin) in it's name

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

DO NOT REPLY [Bug 24504] - Cannot create a document that has accent characters (Latin) in it's name

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

DO NOT REPLY [Bug 24309] - MultiThreadedHttpConnectionManager daemon Thread never GC'd

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

RE: read timeout with persistent connection

2003-11-18 Thread Matthew McGowan
Ortwin Glück write: There is an option to disable stale checking. Thanks, though turning stale checking off doesn't change the outcome - the readResponse call still blocks for 30s. I don't think it's the stale checking that's causing the problem, but for some reason the server ignores or closes