[
https://issues.apache.org/jira/browse/HTTPCLIENT-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226595#comment-16226595
]
Bert Peters commented on HTTPCLIENT-1878:
-----------------------------------------
I am quite sure, though I guess it could be an option. I do not see a warning
about these particular cookies. I do about some others, but those are indeed
invalid. And if they were invalid, why would they mysteriously reappear if you
handle your redirect manually?
> Automatic redirect handling incorrectly parses cookies
> ------------------------------------------------------
>
> Key: HTTPCLIENT-1878
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1878
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (async), HttpClient (classic)
> Affects Versions: 4.5.3
> Environment: Linux, Java 8 OpenJDK
> Reporter: Bert Peters
> Priority: Minor
>
> When a request is handled as a redirect, the HttpClient incorrectly does not
> handle any `SetCookie` headers but instead just starts the redirect.
> This issue affects both the HttpClient and HttpAsyncClient.
> To reproduce:
> # Create two pages, one redirecting to the next.
> # Let the first page set a cookie
> # Dump all cookies sent to the second page
> A current workaround is to handle redirects manually, since that way cookies
> are parsed normally.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
