[jira] Commented: (HTTPCLIENT-810) cookie value parsing

["freetwix (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655979#action_12655979 ] 

freetwix commented on HTTPCLIENT-810:
-------------------------------------

i don't get the point (i understand that httpclient don't want to support all the browser ugliness, though).

the rfc part you bring as a counter-argument is for sending the cookie. there is the only valid use of a comma as a separator, but only for the separation of the cookie-version (nobody seems to use).

but the the important part for me is the parsing of a Set-Cookie header and the note, that a comma as a separator between cookie-values should be supported (which is described again in the sending of the cookie - that's the weak point of the spec). i can't see in the rfc why a comma separated cookie value is split up into multiple cookies. the onyl valid separator is a semicolon!

i don't want to write my own cookie spec, you misunderstood me in this point. there are some arguments that other implementations of cookie parsing seem to handle cookies the way i understand the rfc in this weird case and even jmeter in older versions supported these cookies. now they switched to httpclient (which is a good idea, i think, cause why reinvent the wheel) but that is a problem for me now. especially if httpclient will be the defacto standard for cookie parsing in java world.

i really honour the work you are doing providing the commons for the community, thx.

greets,
freetwix


> cookie value parsing
> --------------------
>
>                 Key: HTTPCLIENT-810
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-810
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpCookie
>    Affects Versions: 3.1 Final
>         Environment: jmeter test (using jmeter 2.3.2)
>            Reporter: freetwix
>
> A cookie is set in a request like this:
>   Set-Cookie: cookiename=|foo=yyy,bar=xxx|; secure; path=/
> The resulting cookie in the next request looks like this:
>   cookiename=|foo=yyy; bar=xxx|;
> as far as i understand, the one cookie is parsed into 2 cookies. jmeter seems to use httpclient-3.1 for the parsing. is this an issue for you?
> greets,
> freetwix

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org