[HTTPCLIENT-1652] AuthSchemeBase.challengeState doesn't survive serialisation in BasicAuthCache

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 4.4.1
• Fix Version/s: 4.5
• Component/s: HttpClient (classic)
• Assignee: Unassigned
• Reporter: Renat Sabitov
• Created: 28/May/15 04:05
• Updated: 04/May/17 09:49
• Resolved: 28/May/15 13:12

Description

If a BasicScheme with ChallengeState defined is put in a BasicAuthCache, it comes out of the cache with null challengeState.

This is a small test to demonstrate the problem:

    @Test
    public void assertChallengeStateSurvivesSerialisation() throws Exception {
        BasicAuthCache localCache = new BasicAuthCache();
        HttpHost aHost = new HttpHost("sample.host", 80);

        BasicScheme proxyScheme = new BasicScheme();
        proxyScheme.processChallenge(
                new BasicHeader(HttpHeaders.PROXY_AUTHENTICATE, "Basic "));

        assertThat(proxyScheme.getChallengeState(), is(ChallengeState.PROXY));

        localCache.put(aHost, proxyScheme);

        BasicScheme outOfCache = (BasicScheme) localCache.get(aHost);
        assertThat(outOfCache.getChallengeState(), is(ChallengeState.PROXY));
    }

result is:

java.lang.AssertionError: 
Expected: is <PROXY>
     but: was null

Issue Links

• duplicates: HTTPCLIENT-1649 Caching of proxy auth schemes is broken
• is related to: CXF-6704 Upgrade to httpclient 4.5.x