[
https://issues.apache.org/jira/browse/HTTPCLIENT-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole SH closed HTTPCLIENT-1788.
------------------------------
> Cookies for paths that are no prefix of the uri path are rejected (using
> CookieSpec Standard)
> ---------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1788
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1788
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Affects Versions: 4.5.2
> Reporter: Ole SH
> Priority: Minor
> Fix For: 4.5.3, 5.0 Alpha2
>
>
> Using CookieSpec Standard if a response to a http request to http://.../abc
> contains a cookie for the path /def this cookie is rejected by httpclient.
> This is the correct behavior in case of [RFC
> 2109|https://www.ietf.org/rfc/rfc2109.txt] (cf. HTTPCLIENT-1043). But [RFC
> 6265|https://tools.ietf.org/html/rfc6265] (as far as I know) does not state
> that a cookie path must be a prefix of the request uri path. In 8.6 it is
> even mentioned as a "security problem" that 'an HTTP response to a request
> for http://example.com/foo/bar can set a cookie with a Path attribute of
> "/qux"'.
> I know that I can workaround my problem by using a custom cookie policy. I
> just wondered if this behavior of httpclient is correct with respect to RFC
> 6265.
> cf.
> http://mail-archives.apache.org/mod_mbox/hc-httpclient-users/201611.mbox/%[email protected]%3E
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
