IETF Logo Mail Archive

Re: [http-state] non-ASCII cookie values (was Re: Closing Ticket 3: Public Suffixes)

Adam Barth <ietf@adambarth.com> Wed, 03 February 2010 08:34 UTC

Return-Path: <adam@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 537A23A68F0 for <http-state@core3.amsl.com>; Wed, 3 Feb 2010 00:34:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level:
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[AWL=0.128, 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 r4s31vCppeqp for <http-state@core3.amsl.com>; Wed, 3 Feb 2010 00:34:35 -0800 (PST)
Received: from mail-px0-f186.google.com (mail-px0-f186.google.com [209.85.216.186]) by core3.amsl.com (Postfix) with ESMTP id 932D63A6A66 for <http-state@ietf.org>; Wed, 3 Feb 2010 00:34:35 -0800 (PST)
Received: by pxi16 with SMTP id 16so13102pxi.29 for <http-state@ietf.org>; Wed, 03 Feb 2010 00:35:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.142.5.39 with SMTP id 39mr1250110wfe.196.1265186114199; Wed, 03 Feb 2010 00:35:14 -0800 (PST)
In-Reply-To: <4B692F9F.7040602@gmx.de>
References: <7789133a1002011014x5d587436j663a73bc92270a65@mail.gmail.com> <143E98B7-BFA6-4F77-9685-E57FFD2449A6@apple.com> <7789133a1002021737v2a50be07u3eea61a2fe870c79@mail.gmail.com> <4B6926FC.5030107@gmx.de> <67660F71-01A3-4B66-B546-B740A1314E49@apple.com> <7789133a1002022348h57a61611me73b95e110c72ea3@mail.gmail.com> <4B692D7C.900@gmx.de> <7789133a1002030006r1d9b1bech491fa7826587eaff@mail.gmail.com> <7789133a1002030008n4f4e294fn548c359133d7734b@mail.gmail.com> <4B692F9F.7040602@gmx.de>
From: Adam Barth <ietf@adambarth.com>
Date: Wed, 03 Feb 2010 00:34:54 -0800
Message-ID: <7789133a1002030034w5400ddb8k61bf9d7be880c2c0@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: http-state@ietf.org
Subject: Re: [http-state] non-ASCII cookie values (was Re: Closing Ticket 3: Public Suffixes)
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: Wed, 03 Feb 2010 08:34:36 -0000

On Wed, Feb 3, 2010 at 12:11 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> Adam Barth wrote:
>> ...
>> Those cases being charset0001, charset0002, and charset0003.  One
>> possible explanation is that Safari rejects cookies that have
>> non-ASCII characters in their values.
>> ...
>
> ...which I think is not really a bug, according to the specs.

I'm not sure that's the most important consideration.

> Unless that affects Safari's interoperability, I'd strongly recommend to
> consider making this the recommended behavior.

Why?  Ideally, a justification would be an evidence-based argument we
could use to convince the implementors of IE, Firefox, Chrome, and
Opera that the benefits of changing their behavior out-weighs the
costs.

In general, I'm very reluctant to specify a behavior that conflicts
with IE, Firefox, Chrome, and Opera.  In specific, IE has something
like 99% market share in some Asian markets.  The fact that this issue
affects Asian markets disproportionately means the pressure to be
IE-like is even greater than usual.

Adam

v2.23.0 | Report a Bug | By Email