DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34909>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34909 ------- Additional Comments From [EMAIL PROTECTED] 2005-05-17 21:40 ------- It turned out not to be a digest problem. I was reading the "Known Limitations and Problems" here: http://jakarta.apache.org/commons/httpclient/3.0/sslguide.html Since I am using JDK 1.3, I figured I might be having a problem with stale connection checking--which it looks like is enabled by default in httpclient 2.0.2 and 3.0-rc2. I shut of stale connection checking and it started working in 3.0-rc2. At first, this made no sense because stale connection checking is also enabled in 2.0.2 by default. What is different is the way each version implements isStale(). The version 2.0.2 httpclient uses a PushbackInputStream, while version 3.0-rc2 uses a BufferedInputStream. This may not be a problem in JDK 1.4 at all, but for 1.3 it took a little time to figure out. I'm still not entirely sure why this was causing the problem--my guess is that because the client thought the connection was stale, it re-opened a new one for which the nonce value the client had was no longer valid--hence the 401 status code. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
