Re: HttpRecoverableException

2003-10-31 Thread [EMAIL PROTECTED]
: ... 20031031 11:59:11,055 DEBUG [Checker273] httpclient.HttpConnection - enter HttpConnection.open() 20031031 11:59:14,380 DEBUG [Checker273] httpclient.HttpConnection - enter HttpConnection.print(String) 20031031 11:59:14,380 DEBUG [Checker273] httpclient.HttpConnection - enter

Re: NTLM authentication

2003-10-31 Thread Alfonso
Michael You are right, I was not using the rc2 source but the commons-httpclient-20031022.zip source. However in both cases the wire log is identical (except of course for the timestamps). Here it is [DEBUG] wire - - GET http://www.apache.org/ HTTP/1.1[\r][\n] [DEBUG] wire - - User-Agent:

Re: HttpRecoverableException

2003-10-31 Thread [EMAIL PROTECTED]
Oleg Kalnichevski wrote: IOTimeoutException usually is a wrapper for java.io.InterruptedIOException. I guess the name does not adequately reflect the nature of this exception. I forgot to tell you my opinion about this: the name itself was clear to me, I expected it to be thrown instead of an

Getting 502 Bad Gateway on connection

2003-10-31 Thread Karr, David
I'm apparently using version 2.0-alpha3-dev of HTTPClient. I doubt this is a problem with HTTPClient, but I'm just trying to understand my issue a little better. I have a servlet running in WebLogic on my desktop, and I'm trying to connect to an external URL through an authenticated proxy. My

Re: Getting 502 Bad Gateway on connection

2003-10-31 Thread Eric Johnson
David, Others will undoubtedly suggest this, but if you can, upgrade to the latest HttpClient 2.0 rc2. Numerous bug fixes for proxy support have been made since the release you mention. See if the newer release resolves the problem. If it doesn't, you might follow the instructions for

Re: NTLM authentication

2003-10-31 Thread Oleg Kalnichevski
Alfonso, Nightly builds that you are using contain experimental and unstable code. 2.1 branch is in a state of profound flux. We are still trying to finalise the API and simply have no bandwidth to deal with the bugs in the experimental code. Please retest your application using the latest

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

2003-10-31 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.

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

2003-10-31 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: NTLM authentication

2003-10-31 Thread Oleg Kalnichevski
I posted yesterday a message with the parts of the log that begins with wire, (is that the wire log?) saying that the output log is identical in the two versions of the code (rc2 and nightly). Of course, the fix perhaps is not going the be same for the two versions. That is the correct wire

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

2003-10-31 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.

NTLM authentication

2003-10-31 Thread Alfonso
Oleg Nightly builds that you are using contain experimental and unstable code. 2.1 branch is in a state of profound flux. We are still trying to finalise the API and simply have no bandwidth to deal with the bugs in the experimental code. Please retest your application using the latest official