Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)

Dan Winship <dan.winship@gmail.com> Mon, 31 January 2011 13:56 UTC

Return-Path: <dan.winship@gmail.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 4939B3A6973 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 05:56:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level:
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=-0.832, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311]
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 yZJJGsNVmxM1 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 05:56:20 -0800 (PST)
Received: from mysterion.org (li168-117.members.linode.com [173.230.128.117]) by core3.amsl.com (Postfix) with ESMTP id 8F29A3A67E1 for <http-state@ietf.org>; Mon, 31 Jan 2011 05:56:20 -0800 (PST)
Received: from desktop.home.mysterion.org (c-76-97-71-164.hsd1.ga.comcast.net [76.97.71.164]) by mysterion.org (Postfix) with ESMTPSA id 5B80E34A3D; Mon, 31 Jan 2011 08:59:34 -0500 (EST)
Message-ID: <4D46C045.4070101@gmail.com>
Date: Mon, 31 Jan 2011 08:59:33 -0500
From: Dan Winship <dan.winship@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7
MIME-Version: 1.0
To: Daniel Stenberg <daniel@haxx.se>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com> <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr> <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr> <op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 13:56:21 -0000

On 01/31/2011 06:59 AM, Daniel Stenberg wrote:
>> 5.1.1 (in combination with 2.1) says so.
> 
> That's not my interpretation at all. I can't find any mention of the
> algorithm having to skip "rubbish" in the date field and continue
> parsing on after it.

"The user agent MUST use an algorithm equivalent to the following
algorithm to parse a cookie-date." If you reject some dates that the
5.1.1 algorithm would accept, then your algorithm is not equivalent.

(Likewise if you accept some strings that the 5.1.1 algorithm rejects,
or interpret any accepted string as referring to a different date than
the 5.1.1 algorithm does.)

-- Dan