[
https://issues.apache.org/jira/browse/HTTPCLIENT-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCLIENT-667:
-----------------------------------------
Fix Version/s: (was: 4.0 Alpha 2)
4.0 Alpha 3
> Provide BestMatch cookie policy
> -------------------------------
>
> Key: HTTPCLIENT-667
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-667
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpCookie
> Reporter: Oleg Kalnichevski
> Fix For: 4.0 Alpha 3
>
>
> Presently HttpClient uses a single cookie policy for all target hosts, which
> is suboptimal for two reasons:
> (1) the user needs to know beforehand what kind of HTTP cookie support the
> target host provides
> (2) does not work well with multiple sites with different level of HTTP
> cookie support
> Introduce new cookie policy that dynamically picks up a CookieSpec (browser
> compatibility | Netscape draft | RFC2109 | RFC2965) based on properties of
> the response received from the target host
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
