cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "iris ding (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-6729) Version 1 NewCookie is not compliant with RFC 2109
Date Tue, 12 Jan 2016 09:29:40 GMT

    [ https://issues.apache.org/jira/browse/CXF-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093599#comment-15093599
] 

iris ding commented on CXF-6729:
--------------------------------

Thnaks Sergey. The fix from Neal looks good to me. The difference between Neal and Jersey
implementation is Jersy will always set "" when it encounters special characters while Neal's
version will check the cookie version first and only set "" if it is a version 1 cookie.

Let us know your thoughts about this. I will be glad to commit the final change into CXF 
as my first commit.

By the way, what branch should I commit to? 

Thanks & Best Regards,

Iris Ding

>  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, NewCookieHeaderProviderTest.java,
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)

Mime
View raw message