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-24 14:07 ------- Mike, my assumption is that the presence of (extra) Proxy-Authorization header prompts the NTLM proxy to invalidate the authorization for the given connection and force re-authentication. As HttpClient assumes that it has already attempted authentication against the said proxy, it just gives up. I do not know NTLM authentication in great details, so I may be wrong here, but the main difference to digest and basic authentication schemes is that NTLM scheme is connection oriented. Once the agent has been successfully authenticated with an NTLM authentication authority, user identity is propagated to all the following requests as long as connection is kept alive, whereas digest and basic authentication schemes are request oriented and thus must include Proxy-Authorization | Authorization directive with every request. Currently HttpClient does not differenciate connection and request oriented schemes. I can well be wrong in my assumptions, but the empirical evidence seems to support them so far. After all, my initial patch did fix the problem with NTLM authentication. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
