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

Adam Barth <ietf@adambarth.com> Mon, 01 February 2010 18:14 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 []) by core3.amsl.com (Postfix) with ESMTP id 8645B3A686A for <http-state@core3.amsl.com>; Mon, 1 Feb 2010 10:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.824
X-Spam-Status: No, score=-1.824 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id H+TCEb03EjQw for <http-state@core3.amsl.com>; Mon, 1 Feb 2010 10:14:06 -0800 (PST)
Received: from mail-iw0-f184.google.com (mail-iw0-f184.google.com []) by core3.amsl.com (Postfix) with ESMTP id B90213A6767 for <http-state@ietf.org>; Mon, 1 Feb 2010 10:14:05 -0800 (PST)
Received: by iwn14 with SMTP id 14so4884169iwn.17 for <http-state@ietf.org>; Mon, 01 Feb 2010 10:14:37 -0800 (PST)
MIME-Version: 1.0
Received: by with SMTP id p25mr3263610wfc.301.1265048077237; Mon, 01 Feb 2010 10:14:37 -0800 (PST)
From: Adam Barth <ietf@adambarth.com>
Date: Mon, 01 Feb 2010 10:14:17 -0800
Message-ID: <7789133a1002011014x5d587436j663a73bc92270a65@mail.gmail.com>
To: eric bianchetti <eric_bianchetti@yahoo.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: http-state@ietf.org
Subject: [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: Mon, 01 Feb 2010 18:14:07 -0000

On Sun, Jan 31, 2010 at 2:37 PM, eric bianchetti
<eric_bianchetti@yahoo.com> wrote:
> That part does not please :
> The cookie-value is opaque to the user agent and MAY be anything the
>    origin server chooses to send, possibly in a server-selected
>    printable ASCII encoding.
> Livng and working in a non ASCII country, I tend to think we shall prepare for the coming of the other languages (Thai, Chines, Korean ....), IF a person get a cookie from a Thai server , can we securely suppose that person(computer) went to a thai site, and that person is using Thai on a daily basis? (Replace Thai by any multi bytes languages).

The part of that sentence after the "possibly" doesn't haven any
normative force (it's just advice that the server can take or leave).
I can remove the reference to ASCII here if you like.  Julian please
correct me if I'm wrong, but I believe that HTTP headers typically
contain only ASCII characters.