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

Mark Pauley <mpauley@apple.com> Thu, 04 March 2010 02:08 UTC

Return-Path: <mpauley@apple.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 346F63A8BA2 for <http-state@core3.amsl.com>; Wed, 3 Mar 2010 18:08:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 4SCEoRJAbNx2 for <http-state@core3.amsl.com>; Wed, 3 Mar 2010 18:08:16 -0800 (PST)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 5BEC93A8B0A for <http-state@ietf.org>; Wed, 3 Mar 2010 18:08:16 -0800 (PST)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out4.apple.com (Postfix) with ESMTP id 4B97C8ED715D; Wed, 3 Mar 2010 18:08:18 -0800 (PST)
X-AuditID: 11807134-b7cd9ae000001002-43-4b8f16127e3d
Received: from il0301a-dhcp53.apple.com (il0301a-dhcp53.apple.com [17.203.14.181]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id E5.66.04098.2161F8B4; Wed, 3 Mar 2010 18:08:18 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: Mark Pauley <mpauley@apple.com>
In-Reply-To: <5c4444771003031754w1768653dt6f0d142205ec3583@mail.gmail.com>
Date: Wed, 3 Mar 2010 18:08:17 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7373C01-7743-4ACF-A4AD-1F22501E1D3F@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> <5c4444771003031754w1768653dt6f0d142205ec3583@mail.gmail.com>
To: Adam Barth <ietf@adambarth.com>
X-Mailer: Apple Mail (2.1078)
X-Brightmail-Tracker: AAAAAQAAAZE=
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 02:08:17 -0000

Perfect.  I'll stay tuned.

On Mar 3, 2010, at 5:54 PM, Adam Barth wrote:

> 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