[HTTPCLIENT-1628] Auth cache can fail when domain name contains uppercase characters

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.4 Final
• Fix Version/s: 4.4.1, 4.5
• Component/s: HttpClient (classic)
• Assignee: Unassigned
• Reporter: Dennis Ju
• Created: 07/Mar/15 01:26
• Updated: 04/May/17 09:48
• Resolved: 11/Mar/15 20:55

Description

Following the example for using preemptive authentication given in the documentation here 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.