[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wink-dev
Subject:    [jira] [Comment Edited] (WINK-422) Handling JSON Cookies
From:       "Andy Yang (JIRA)" <jira () apache ! org>
Date:       2014-03-06 21:31:45
Message-ID: JIRA.12697465.1393451317878.18350.1394141505312 () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/WINK-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922943#comment-13922943 \
] 

Andy Yang edited comment on WINK-422 at 3/6/14 9:31 PM:
--------------------------------------------------------

In the obsoleted RFC-2109 and RFC-2965, commas were specified as being valid cookie \
separators. However, RFC-6265 supercedes both of these and section 4.2.1 specifies \
only semi-colons.


was (Author: ayang):
In the obsoleted RFC-2109 and RFC-2965, commas were specified as being valid cookie \
separators. However, RFC-6265 supercedes both of these and section 4.2.1 specifies \
only semi-colons.

It seems this would be a trivial fix in \
org.apache.wink.server.internal.contexts.HttpheadersImpl. 

> Handling JSON Cookies
> ---------------------
> 
> Key: WINK-422
> URL: https://issues.apache.org/jira/browse/WINK-422
> Project: Wink
> Issue Type: Improvement
> Components: Server
> Affects Versions: 1.4
> Reporter: Andy Yang
> 
> currently HttpHeadersImpl's parseCookieHeader() method does a split("[;,]") on the \
> cookie header which doesn't handle case where cookie values are JSON which are full \
> of commas. Religious convictions aside, JSON cookies are fairly common - would Wink \
> consider implementing some way of accessing them, or will it be left up to the user \
> to retrieve the raw header and extract the cookies manually?



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[prev in list] [next in list] [prev in thread] [next in thread]