Hi Oleg,
>
> Given it is a very common protocol violation HttpClient ships with a
> number of cookie policies (BROWSER_COMPATIBILITY, NETSCAPE_DRAFT as well
> as BEST_MATCH) that are capable of parsing such headers. There is
> nothing special one needs to do. Simply let HttpClient's default cooki
On Fri, 2012-11-09 at 16:18 +0100, pvbem...@xs4all.nl wrote:
> Hi Jean-Marc, Oleg,
>
> Thanks for your replies.
>
> I think I found the relevant part of the spec:
>
> rfc2616.pdf: page 17:
> Many HTTP/1.1 header field values consist of words separated by LWS
> or special characters. These sp
Hi Jean-Marc, Oleg,
Thanks for your replies.
I think I found the relevant part of the spec:
rfc2616.pdf: page 17:
Many HTTP/1.1 header field values consist of words separated by LWS
or special characters. These special characters MUST be in a quoted
string to be used within a parameter va
On Wed, 2012-11-07 at 19:43 +0100, pvbem...@xs4all.nl wrote:
> Hi JM,
>
> Look again: the ',' in
>
>"expires=Sun, 03-Nov-2013 10:54:41 GMT;"
>
> is parsed as if it were a ';' .
>
> That leads to
> expires=Sun
> and
> 03-Nov-2013 10:54:41 GMT=null
>
> I can't believe I'm the fir
Oh! I see!
This is working fine:
response.addHeader("Set-Cookie", "c2=b; expires=\"Sun, 03-Nov-2013
10:54:41 GMT\"; path=\"/\", c3=c; domain=\"localhost\"");
2012/11/7, pvbem...@xs4all.nl :
>
> Hi JM,
>
> Look again: the ',' in
>
>"expires=Sun, 03-Nov-2013 10:54:41 GMT;"
>
> is parse
Hi JM,
Look again: the ',' in
"expires=Sun, 03-Nov-2013 10:54:41 GMT;"
is parsed as if it were a ';' .
That leads to
expires=Sun
and
03-Nov-2013 10:54:41 GMT=null
I can't believe I'm the first person to notice this...
Paul.
>
>Hi Paul,
>
>I don't see anything wrong with the
