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=24352>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24352 NLTM Proxy and basic host authorization ------- Additional Comments From [EMAIL PROTECTED] 2003-11-03 12:36 ------- As I can see, one possible way of solving the problem is to "forget" the list of realms used for proxy authentication when trying the validation after receiving the "401" from the remote host. This can be done by changing in HttpMethodBase#processAuthenticationResponse. In lines 2476-2484 it says case HttpStatus.SC_UNAUTHORIZED: challenges = getResponseHeaderGroup().getHeaders(HttpAuthenticator.WWW_AUTH); realmsUsed = realms; host = conn.getVirtualHost(); if (host == null) { host = conn.getHost(); } break; Clearing the list of realms used for the proxy could be something like case HttpStatus.SC_UNAUTHORIZED: challenges = getResponseHeaderGroup().getHeaders(HttpAuthenticator.WWW_AUTH); proxyRealms.clear(); realmsUsed = realms; host = conn.getVirtualHost(); if (host == null) { host = conn.getHost(); } break; Recompiling after this change and trying again the test case retrieves the page just fine (do I have to attach a log?) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
