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

Adam Barth <ietf@adambarth.com> Tue, 09 February 2010 18:19 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 2629B3A6919 for <http-state@core3.amsl.com>; Tue, 9 Feb 2010 10:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.846
X-Spam-Level:
X-Spam-Status: No, score=-1.846 tagged_above=-999 required=5 tests=[AWL=0.131, 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 2sTRt5lN8fAr for <http-state@core3.amsl.com>; Tue, 9 Feb 2010 10:19:42 -0800 (PST)
Received: from mail-yw0-f185.google.com (mail-yw0-f185.google.com [209.85.211.185]) by core3.amsl.com (Postfix) with ESMTP id 4AD0B3A6870 for <http-state@ietf.org>; Tue, 9 Feb 2010 10:19:42 -0800 (PST)
Received: by ywh15 with SMTP id 15so1610816ywh.5 for <http-state@ietf.org>; Tue, 09 Feb 2010 10:20:46 -0800 (PST)
MIME-Version: 1.0
Received: by 10.142.249.10 with SMTP id w10mr5594975wfh.207.1265739646119; Tue, 09 Feb 2010 10:20:46 -0800 (PST)
In-Reply-To: <7789133a1002030847s106f9849vbfdc793949ce832c@mail.gmail.com>
References: <7789133a1002021958g49bad0c4s4472ecb046f28c5e@mail.gmail.com> <4B698717.20208@gmail.com> <7789133a1002030847s106f9849vbfdc793949ce832c@mail.gmail.com>
From: Adam Barth <ietf@adambarth.com>
Date: Tue, 9 Feb 2010 10:20:26 -0800
Message-ID: <7789133a1002091020q4093287drb607e8a9985546e4@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: Tue, 09 Feb 2010 18:19:43 -0000

Done.

On Wed, Feb 3, 2010 at 8:47 AM, Adam Barth <ietf@adambarth.com> wrote:
> 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
>>
>