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

Daniel Stenberg <daniel@haxx.se> Wed, 03 March 2010 20:53 UTC

Return-Path: <daniel@haxx.se>
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 9CACC3A89E0 for <http-state@core3.amsl.com>; Wed, 3 Mar 2010 12:53:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 yV6PCs3DGUQq for <http-state@core3.amsl.com>; Wed, 3 Mar 2010 12:53:26 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [83.168.254.42]) by core3.amsl.com (Postfix) with ESMTP id 348A13A82F0 for <http-state@ietf.org>; Wed, 3 Mar 2010 12:53:23 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [83.168.254.42]) by giant.haxx.se (8.14.3/8.14.3/Debian-9) with ESMTP id o23KrCJJ020784; Wed, 3 Mar 2010 21:53:12 +0100
Date: Wed, 3 Mar 2010 21:53:12 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Mark Pauley <mpauley@apple.com>
In-Reply-To: <CB794A2E-2F2F-4CE4-8B15-BBE1A1E1B50F@apple.com>
Message-ID: <alpine.DEB.2.00.1003032150381.3143@tvnag.unkk.fr>
References: <5c4444771003021624qc0b00cet27e348cb6d023b08@mail.gmail.com> <CB794A2E-2F2F-4CE4-8B15-BBE1A1E1B50F@apple.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: 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: Wed, 03 Mar 2010 20:53:27 -0000

On Wed, 3 Mar 2010, Mark Pauley wrote:

> In the future, we ought to treat these as opaque octets.  However, the 
> current cookie spec would lead me to believe that we should reject any 
> cookies that contain control characters, which would be most non-ascii UTF-8 
> sequences, right?

Isn't the RFC2616 'token' a bit too strict for cookie-value ? The netscape 
spec is _very_ liberal ("a sequence of characters excluding semi-colon, comma 
and white space") so the current wording is a great deal more restrictive.

Don't cookie implementations already allow and use for example ()<>:@? etc?

-- 

  / daniel.haxx.se