Re: [http-state] Ticket 11: Character encoding for non-ASCII cookies values

[Adam Barth <[e-mail]>]

On Wed, Mar 3, 2010 at 5:24 PM, Mark Pauley <[e-mail]> wrote:
> On Mar 3, 2010, at 5:17 PM, Adam Barth wrote:
>> If you haven't already, I'd encourage you to read the latest draft
>> available at <http://tools.ietf.org/html/draft-ietf-httpstate-cookie>.
>> Hopefully that will answer some number of your questions.
>
> Interesting.  Well, this could certainly simplify much of our internal cookie parsing mechanism.  Is there going to be a push to deprecate RFC2109?

Our charter is to depreciate RFC2109 in favor of the spec we're writing.

> Could you point me at a page with results on how the browsers handle different Set-Cookie forms in practice?  Changing our behavior is nearly always dictated by broken compatibility with other sites.

We're going to produce such a document once the spec settles down a
bit more.  Currently, the best documentation we have is the spec
itself and the test suite I referenced before.  The spec is intended
to be very close to how browsers actually behave.  In particular, IE,
Firefox, and Chrome pass the vast majority of the tests in the test
suite.

If you have a question about a specific form, I can usually tell you
the compatibility matrix.  If I can't, that means we need to write
more tests.  :)

Adam