[
https://issues.apache.org/jira/browse/CXF-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229153#comment-15229153
]
Sergey Beryozkin commented on CXF-6729:
---------------------------------------
Neal, where you exactly you saw the text that all of the special characters
have to be quoted in various cookie properties ?
See https://issues.apache.org/jira/browse/CXF-6862.
Example, '/' is obviously OK for Path and quoting it causes side-effects now.
I've checked the linked Jersey code - it looks like it only quotes the values
if white spaces are there.
This is what I'm going to do with our code too, unless you can confirm that
quoting other characters is also critical ?
> Version 1 NewCookie is not compliant with RFC 2109
> ---------------------------------------------------
>
> Key: CXF-6729
> URL: https://issues.apache.org/jira/browse/CXF-6729
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.0.7, 3.1.4
> Environment: Windows
> Reporter: Neal Hu
> Fix For: 3.1.5, 3.0.8
>
> Attachments: NewCookieHeaderProvider.java,
> NewCookieHeaderProvider.patch, NewCookieHeaderProviderTest.java,
> NewCookieHeaderProviderTest.patch, ResponseImplTest.java
>
>
> Hi,
> From http://www.ietf.org/rfc/rfc2109.txt and
> http://stackoverflow.com/questions/572482/why-do-cookie-values-with-whitespace-arrive-at-the-client-side-with-quotes
> the version 1 cookie look like: name="value with
> spaces";Max-Age=3600;Path="/";Version=1
> NewCookieHeaderProvider.toString(NewCookie) has not handled the special
> characters(RFC2068) that need around with quotes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
