Re: [http-state] A non-string cookie API (was: non-ASCII cookie values)

Adam Barth <ietf@adambarth.com> Wed, 03 February 2010 16:47 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 5CF1D28C198 for <http-state@core3.amsl.com>; Wed, 3 Feb 2010 08:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.829
X-Spam-Level:
X-Spam-Status: No, score=-1.829 tagged_above=-999 required=5 tests=[AWL=0.148, 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 3wa+ztk299Mz for <http-state@core3.amsl.com>; Wed, 3 Feb 2010 08:47:16 -0800 (PST)
Received: from mail-pz0-f175.google.com (mail-pz0-f175.google.com [209.85.222.175]) by core3.amsl.com (Postfix) with ESMTP id 0237F28C19E for <http-state@ietf.org>; Wed, 3 Feb 2010 08:47:15 -0800 (PST)
Received: by pzk5 with SMTP id 5so2700628pzk.29 for <http-state@ietf.org>; Wed, 03 Feb 2010 08:47:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.142.8.14 with SMTP id 14mr5206019wfh.59.1265215676308; Wed, 03 Feb 2010 08:47:56 -0800 (PST)
In-Reply-To: <4B698717.20208@gmail.com>
References: <7789133a1002021958g49bad0c4s4472ecb046f28c5e@mail.gmail.com> <4B698717.20208@gmail.com>
From: Adam Barth <ietf@adambarth.com>
Date: Wed, 3 Feb 2010 08:47:36 -0800
Message-ID: <7789133a1002030847s106f9849vbfdc793949ce832c@mail.gmail.com>
To: Dan Winship <dan.winship@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Daniel Stenberg <daniel@haxx.se>, http-state@ietf.org
Subject: Re: [http-state] A non-string cookie API (was: non-ASCII cookie 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 Feb 2010 16:47:17 -0000

I think what you're suggesting is to make this advice non-normative,
which seems like a good idea.

Adam


On Wed, Feb 3, 2010 at 6:24 AM, Dan Winship <dan.winship@gmail.com> wrote:
> On 02/02/2010 10:58 PM, Adam Barth wrote:
>>> (And likewise, the spec could recommend that web site
>>> frameworks/libraries SHOULD provide similar idiot-proof high-level
>>> cookie APIs, rather than expecting authors to generate valid Set-Cookie
>>> headers by themselves.)
>>
>> We can get input from long-time IETF folks, but my understanding is
>> that the spec should keep its normative requirements focused on
>> protocol messages.
>
> OK, maybe s/SHOULD/should/ then, but see below too.
>
> On 02/03/2010 02:42 AM, Daniel Stenberg wrote:
>> Don't we pretty much assume and wish for this for every spec and
>> protocol? I mean, we make a smaller set of libraries and frameworks for
>> everything that then a large amount of users can use.
>>
>> It is really the job of this spec to spell it out?
>
> It's advice based on past implementation experience. We know that lots
> of web site authors are going to generate invalid Set-Cookie headers if
> their APIs let them. So we should encourage framework authors to provide
> better APIs, because that means there will be more valid protocol
> messages going over the wire and fewer invalid ones.
>
> -- Dan
>