[
https://issues.apache.org/jira/browse/HTTPCLIENT-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15785442#comment-15785442
]
Oleg Kalnichevski commented on HTTPCLIENT-1006:
-----------------------------------------------
There is no point moving anywhere given that your entire line of reasoning is
based on a completely wrong premise.
As far as RFC 6265 goes I would like to understand whether the new spec
intended to provide some degree of backward compatibility with previous specs
and whether or not there is a reference to a generic mechanism for escaping
special characters in header elements. For that I need to revisit the entire
chain of RFCs which is likely to take a few days. Otherwise the discussion is
pointless because I personally see no evidence in the spec supporting this
statement as well
bq. So a cookie whose value came in DQs also has to be sent back in DQs.
The spec does not state that. It is just your interpretation.
Oleg
> BrowserCompatSpec: don't trim " around cookie value
> ---------------------------------------------------
>
> Key: HTTPCLIENT-1006
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1006
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 4.0.2
> Reporter: Marc Guillemot
>
> If the server sends a cookie header like:
> Set-Cookie: first="hello world"
> then HttpClient parses it as cookie with value >hello world<, wrongly
> removing the leading and trailing quotes. The incorrect quote removal occurs
> in BasicHeaderValueParser.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
