Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: "Commons HttpClient Project"
 <commons-httpclient-dev@jakarta.apache.org>
Date: 14 Jan 2004 21:05:21 -0000
Message-ID: <20040114210521.17477.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: commons-httpclient-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 15297]  -
    [HttpClient] Authenticator() - ability to perform alternate authentication

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=15297>.
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=15297

[HttpClient] Authenticator() - ability to perform alternate authentication


------- Additional Comments From olegk@apache.org  2004-01-14 21:05 -------
>  - Should HttpMethodDirector have it's own version of the auth defaults?  
> It seems like this should be left to the params.

I did not feel like giving users the possibility to mess around with the default
authentication preferences to avoid their misuse. Therefore I wanted to keep the
DEFAULT_AUTH_PREFS private. On the other hand I do agree that HttpClientParams
or AuthPolicy would be a better home for auth defaults.

>  - When new schemes are added, they will have to be added to the 
> AuthPolicy.AUTH_SCHEME_PRIORITY param in order to work.  
> This should probably be documented in AuthPolicy.registerAuthScheme().

Good point. I just realised that this is quite lousy. I think auth defaults
should be derived from the AuthPolicy. I'll try to come up with a better solution. 

A new patch to follow.

Thanks, Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org