[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Kalnichevski resolved HTTPCLIENT-424.
------------------------------------------

    Resolution: Fixed

I am very pleasantly surprised at how easy it turned out to add support for 
preemptive authentication using DIGEST. 

HttpClient 4.0 rocks!!!!

DIGEST preemptive:

http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/module-client/src/examples/org/apache/http/examples/client/ClientPreemptiveDigestAuthentication.java

BASIC preemptive:

http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/module-client/src/examples/org/apache/http/examples/client/ClientPreemptiveBasicAuthentication.java

Oleg

> setAuthPreemptive restricted to BASIC AuthScheme
> ------------------------------------------------
>
>                 Key: HTTPCLIENT-424
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-424
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpAuth
>    Affects Versions: 3.0 Beta 1
>         Environment: Operating System: Windows 2000
> Platform: PC
>            Reporter: Aaron Hamid
>             Fix For: 4.0 Alpha 5 
>
>         Attachments: preemptiveauth.patch
>
>
> Pre-emptive authentication is hardcoded to be restricted to the BASIC
> authentication scheme.  To fully support custom authentication schemes,
> pre-emptive authentication should be made configurable, either globally, or 
> on a
> per-scheme basis.  A potential compromise may be to require AuthSchemes to
> report whether they support pre-emptive capability if we wish to explicitly
> exclude certain schemes from pre-emptive authentication.
> (reported against 3.0 RC 1)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to