[
https://issues.apache.org/jira/browse/HTTPCLIENT-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-1628.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 4.5 Alpha1
4.4.1
> Auth cache can fail when domain name contains uppercase characters
> ------------------------------------------------------------------
>
> Key: HTTPCLIENT-1628
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1628
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpAuth
> Affects Versions: 4.4 Final
> Reporter: Dennis Ju
> Priority: Minor
> Fix For: 4.4.1, 4.5 Alpha1
>
>
> Following the example for using preemptive authentication given in the
> documentation
> [here|http://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html]
> will fail to authenticate if you use uppercase characters in the domain name
> like loCalHoST or aPache.org.
> This is a new issue with 4.4 because of the new constructor AuthScope(final
> HttpHost origin, final String realm, final String schemeName). This
> constructor differs from the original constructor AuthScope(final String
> host, final int port, final String realm, final String schemeName) where the
> hostname is converted to lowercase. The example uses the latter constructor
> when it creates the AuthScope, so the hostname is lowercase. When a request
> is executed, BasicCredentialsProvider.matchCredentials(...) will try to
> compare this lowercase hostname with a newly created AuthScope that doesn't
> convert to lowercase, so it always returns false.
> The easy fix would be to convert the hostname to lowercase for the first
> constructor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
