Re: [http-state] Is this an omission in the parser rules ofdraft-ietf-httpstate-cookie-21?

Dan Winship <dan.winship@gmail.com> Wed, 16 February 2011 13:29 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 6C09D3A6E07 for <http-state@core3.amsl.com>; Wed, 16 Feb 2011 05:29:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level:
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[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 9Pdkg0JUpALI for <http-state@core3.amsl.com>; Wed, 16 Feb 2011 05:29:44 -0800 (PST)
Received: from mysterion.org (li168-117.members.linode.com [173.230.128.117]) by core3.amsl.com (Postfix) with ESMTP id 26BC13A6DBC for <http-state@ietf.org>; Wed, 16 Feb 2011 05:29:44 -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 6A79934A3E; Wed, 16 Feb 2011 08:30:10 -0500 (EST)
Message-ID: <4D5BD15A.7000605@gmail.com>
Date: Wed, 16 Feb 2011 08:30:02 -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: Remy Lebeau <remy@lebeausoftware.org>
References: <20110204184735.26023.qmail@mm01.prod.mesa1.secureserver.net><AANLkTi=qBVkGwMHqAidtwP5_A8pPrF-Y9MV4jgYS5_QM@mail.gmail.com><7384878F-C44A-42A4-9694-1BB1C18AA5E6@gbiv.com><AANLkTinFq7bE_e3SSgdjuFvZ8hGn1xy4Hc1VKwc=vp1D@mail.gmail.com><49225418-A1AF-4299-8C4F-2E608D34265D@gbiv.com><AANLkTimrJF3LFR4t4j=U2L33kFh+wf-R=sjjwexcmyPi@mail.gmail.com> <26240DE2-4DD3-4863-81B1-635D34BA4AE4@gbiv.com> <26A4B40A07EF489C882815971D7BC38E@RYANLAPTOP>
In-Reply-To: <26A4B40A07EF489C882815971D7BC38E@RYANLAPTOP>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: http-state@ietf.org
Subject: Re: [http-state] Is this an omission in the parser rules ofdraft-ietf-httpstate-cookie-21?
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, 16 Feb 2011 13:29:45 -0000

On 02/16/2011 02:04 AM, Remy Lebeau wrote:
> Since the cookie has a Version=1 attribute, it is an RFC 2109 cookie,
> and RFC 2109 allows Netscape-style date/time formatting:
> 
>    Wdy, DD-Mon-YYYY HH:MM:SS GMT

Not that any of this is in any way relevant, but, no it doesn't. RFC
2109 doesn't allow the Expires attribute at all. A cookie that contains
both "Version=1" and "Expires=..." does not conform to *any* spec.

-- Dan