hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1650) Fluent Executor doesn't inherit auth scheme and creds provider of HttpClient instance
Date Sat, 23 May 2015 08:57:17 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557228#comment-14557228
] 

Oleg Kalnichevski commented on HTTPCLIENT-1650:
-----------------------------------------------

I am quite sure Executor overwrites creds provider only (as well as auth cache). Auth scheme
registry from the HttpClient instance should still apply. I personally think that Executor
overwriting the creds provider and the auth cache is OK. What is not OK is how HttpClient
deals with system wide auth credentials for complex auth schemes such as Win Native, SPNEGO,
etc, but this is something that can only be fixed in 5.0. 

Oleg

> Fluent Executor doesn't inherit auth scheme and creds provider of HttpClient instance
> -------------------------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1650
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1650
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: Fluent HC
>    Affects Versions: 4.4.1
>         Environment: Windows Server 2008
>            Reporter: Alexandre
>              Labels: flexibility
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> When instantiating an Executor from an existing HttpClient instance, the Executor doesn't
inherit the registry of authentication schemes and the credentials provider.
> For instance, to perform an HTTP request using the Windows integrated authentication,
the following will correctly authenticate:
> WinHttpClients.createDefault().execute(new HttpGet(...));
> But this will not:
> Executor.newInstance(defaultWinHttpClient).execute(Request.Get(...))
> I think that this behavior is very counter-intuitive and limiting at the same time. When
an Executor is instantiated from an HttpClient instance, all configurations from that instance
should be taken in account.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message