Adding more confusion to the pile, HTML5[1] now specifies that JavaScript can
set Unicode characters through document.cookie and that they must be encoded as
UTF-8 in the header. Quick testing with Chrome shows it does just that (i.e.
U+00E1 is sent as 0xC3 0xA1). If client and server-side appli
On Jan 1, 2014, at 8:59 AM, Mark Thomas wrote:
> Signed PGP part
> On 26/12/2013 19:23, Jeremy Boynes wrote:
> > On Dec 26, 2013, at 2:47 AM, Mark Thomas wrote:
> >
> > Focusing on the 8-bit issue address by the patch, leaving the other
> > RFC6265 thread for broader discussion ...
> >
> >>> The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/12/2013 19:23, Jeremy Boynes wrote:
> On Dec 26, 2013, at 2:47 AM, Mark Thomas wrote:
>
> Focusing on the 8-bit issue address by the patch, leaving the other
> RFC6265 thread for broader discussion ...
>
>>> The change only allows these charac
On Dec 26, 2013, at 2:47 AM, Mark Thomas wrote:
Focusing on the 8-bit issue address by the patch, leaving the other RFC6265
thread for broader discussion ...
>> The change only allows these characters in values if version == 0
>> where Netscape’s rather than RFC2109’s syntax applies (per the
>>
On 24/12/2013 18:06, Jeremy Boynes wrote:
> On Dec 24, 2013, at 2:29 AM, Mark Thomas wrote:
>
>> On 23/12/2013 19:15, jboy...@apache.org wrote:
>>> Author: jboynes Date: Mon Dec 23 19:15:35 2013 New Revision:
>>> 1553187
>>>
>>> URL: http://svn.apache.org/r1553187 Log: fix #55917 by allowing
>>>
On Dec 24, 2013, at 2:29 AM, Mark Thomas wrote:
> On 23/12/2013 19:15, jboy...@apache.org wrote:
>> Author: jboynes
>> Date: Mon Dec 23 19:15:35 2013
>> New Revision: 1553187
>>
>> URL: http://svn.apache.org/r1553187
>> Log:
>> fix #55917 by allowing 8-bit ISO-8859-1 characters in V0 cookie valu
