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

Daniel Stenberg <daniel@haxx.se> Mon, 31 January 2011 11:56 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 109E53A6915 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 03:56:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[AWL=-0.948, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_51=0.6]
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 xb7HQoVRcOpX for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 03:56:46 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id AD3FE3A68DF for <http-state@ietf.org>; Mon, 31 Jan 2011 03:56:45 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0VBxv79017436; Mon, 31 Jan 2011 12:59:57 +0100
Date: Mon, 31 Jan 2011 12:59:57 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Anne van Kesteren <annevk@opera.com>
In-Reply-To: <op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local>
Message-ID: <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr>
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>
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: IETF HTTP State WG <http-state@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
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 11:56:47 -0000

On Mon, 31 Jan 2011, Anne van Kesteren wrote:

>>>> "Thu, 999999999999-Aug-2007 20:49:07 GMT" or "Sat, 15-Apr-17 boink:z 
>>>> 21:01:22".
>>> 
>>> That would mean it is not compliant.
>> 
>> Sorry, can you please point out what section that says so?
>
> 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.

Or what did you mean with not compliant? For the above two examples, what 
would you claim the spec says the algorithm should do?

-- 

  / daniel.haxx.se