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

Adam Barth <ietf@adambarth.com> Thu, 04 March 2010 01:54 UTC

Return-Path: <ietf@adambarth.com>
X-Original-To: http-state@core3.amsl.com
Delivered-To: http-state@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB36728C25C for <http-state@core3.amsl.com>; Wed, 3 Mar 2010 17:54:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C7yMIGj+k-9W for <http-state@core3.amsl.com>; Wed, 3 Mar 2010 17:54:34 -0800 (PST)
Received: from mail-gx0-f217.google.com (mail-gx0-f217.google.com [209.85.217.217]) by core3.amsl.com (Postfix) with ESMTP id 270EB3A89EF for <http-state@ietf.org>; Wed, 3 Mar 2010 17:54:33 -0800 (PST)
Received: by gxk9 with SMTP id 9so878050gxk.8 for <http-state@ietf.org>; Wed, 03 Mar 2010 17:54:32 -0800 (PST)
Received: by 10.101.145.15 with SMTP id x15mr3853708ann.119.1267667672321; Wed, 03 Mar 2010 17:54:32 -0800 (PST)
Received: from mail-yx0-f187.google.com (mail-yx0-f187.google.com [209.85.210.187]) by mx.google.com with ESMTPS id 35sm25353yxh.33.2010.03.03.17.54.31 (version=SSLv3 cipher=RC4-MD5); Wed, 03 Mar 2010 17:54:31 -0800 (PST)
Received: by yxe17 with SMTP id 17so955855yxe.32 for <http-state@ietf.org>; Wed, 03 Mar 2010 17:54:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.91.122.6 with SMTP id z6mr912064agm.48.1267667670451; Wed, 03 Mar 2010 17:54:30 -0800 (PST)
In-Reply-To: <F5AA8646-DD59-4B2F-A731-6673BAAEC51A@apple.com>
References: <5c4444771003021624qc0b00cet27e348cb6d023b08@mail.gmail.com> <CB794A2E-2F2F-4CE4-8B15-BBE1A1E1B50F@apple.com> <alpine.DEB.2.00.1003032150381.3143@tvnag.unkk.fr> <6EFCDA9A-C4AA-479D-895B-F9229FCF8AB3@apple.com> <5c4444771003031717n390ce79fkdebdfcf51693d877@mail.gmail.com> <F5AA8646-DD59-4B2F-A731-6673BAAEC51A@apple.com>
From: Adam Barth <ietf@adambarth.com>
Date: Wed, 3 Mar 2010 17:54:10 -0800
Message-ID: <5c4444771003031754w1768653dt6f0d142205ec3583@mail.gmail.com>
To: Mark Pauley <mpauley@apple.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Daniel Stenberg <daniel@haxx.se>, http-state <http-state@ietf.org>
Subject: Re: [http-state] Ticket 11: Character encoding for non-ASCII cookies values
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-state>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2010 01:54:35 -0000

On Wed, Mar 3, 2010 at 5:24 PM, Mark Pauley <mpauley@apple.com> 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