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=25529>. 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=25529 Redesign of HTTP authentication framework [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2004-03-24 13:30 ------- Prompted by the 2.0 incompatibility discovered by Vincent Massol <vmassol at pivolis.com> (Specials thanks go to Gump and all the Gump Meisters) I went over the authentication code one more time and made yet another series of changes * I factored out the authentication challenge processing logic from the HttpMethodDirector to a class of its own. Thanks to that authentication challenge processing can now be tested separately. Test cases provided. * HttpMethodDirector no longer intervenes if Authorization & Proxy-Authorization are set manually by the user. Custom authorization headers are never overwritten * Introduced a new class called AuthState that represents the authentication process state that contains all the authentication details. Basically it is just a convenience wrapper around the authentication scheme interface. * Proxy and host authentication state objects moved to the HTTP method level, so that they can be queried by the user to find out the details about authentication that has been performed by the HttpMethodDirector. With the current implementation all the details of proxy and host authentication are contained within the HttpMethodDirector instance, which exists only within the lifetime of HttpClient#executeMethod() execution. As soon as the method returns, the respective HttpMethodDirector instance gets GCed along with the authentication details * More test cases Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
