You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Timo Kinnunen (JIRA)" <ji...@apache.org> on 2014/10/03 17:49:35 UTC
[jira] [Commented] (HTTPCLIENT-1556) Default CookieSpecs provider
not found for AbstractHttpClient subclass
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158112#comment-14158112 ]
Timo Kinnunen commented on HTTPCLIENT-1556:
-------------------------------------------
Works in my testing, thanks!
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org