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] [Resolved] (HTTPCLIENT-1556) Default CookieSpecs provider not found for AbstractHttpClient subclass
Date Fri, 03 Oct 2014 08:15:34 GMT

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

Oleg Kalnichevski resolved HTTPCLIENT-1556.
       Resolution: Fixed
    Fix Version/s: 4.4 Beta2

Patch committed to SVN trunk. Please re-test.


> Default CookieSpecs provider not found for AbstractHttpClient subclass
> ----------------------------------------------------------------------
>                 Key: HTTPCLIENT-1556
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1556
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient
>    Affects Versions: 4.4 Alpha1
>            Reporter: Timo Kinnunen
>              Labels: easyfix
>             Fix For: 4.4 Beta2
> When a client based on the deprecated AbstractHttpClient is created without customizing
the default CookieSpecRegistry, the default CookiePolicy is not subsequently found from this
CookieSpecRegistry in org.apache.http.client.protocol.RequestAddCookies.java line 149. The
reason is that RequestAddCookies is looking up the non-deprecated CookieSpecs.DEFAULT (String
value "default") by default but the CookieSpecRegistry was constructed with the deprecated
CookiePolicy.BEST_MATCH (String value "best-match") as the default.
> Adding the line
>         registry.register(
>                 CookieSpecs.DEFAULT,
>                 new BestMatchSpecFactory());
> to org.apache.http.impl.client.AbstractHttpClient::createCookieSpecRegistry method appears
to fix this issue.

This message was sent by Atlassian JIRA

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

View raw message