Re: [http-state] I-D Action:draft-ietf-httpstate-cookie-03.txt

Julian Reschke <julian.reschke@gmx.de> Mon, 22 February 2010 18:25 UTC

Return-Path: <julian.reschke@gmx.de>
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 4695928C199 for <http-state@core3.amsl.com>; Mon, 22 Feb 2010 10:25:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.453
X-Spam-Level:
X-Spam-Status: No, score=-3.453 tagged_above=-999 required=5 tests=[AWL=-0.854, BAYES_00=-2.599]
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 Mc7aw4SOdho3 for <http-state@core3.amsl.com>; Mon, 22 Feb 2010 10:25:39 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 8E93F28C1D9 for <http-state@ietf.org>; Mon, 22 Feb 2010 10:25:35 -0800 (PST)
Received: (qmail invoked by alias); 22 Feb 2010 18:27:19 -0000
Received: from p508FCAE6.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.202.230] by mail.gmx.net (mp025) with SMTP; 22 Feb 2010 19:27:19 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+c5ssGUuecdgy8GMzNT9FtJ96Fe4dPK3T+khikPk IfR0RzHqJSRoFG
Message-ID: <4B82CC7F.4090101@gmx.de>
Date: Mon, 22 Feb 2010 19:27:11 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Achim Hoffmann <ah@securenet.de>
References: <20100213080001.D07A03A73C7@core3.amsl.com> <4B82C8EE.8000107@securenet.de>
In-Reply-To: <4B82C8EE.8000107@securenet.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.59999999999999998
Cc: http-state@ietf.org
Subject: Re: [http-state] I-D Action:draft-ietf-httpstate-cookie-03.txt
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, 22 Feb 2010 18:25:40 -0000

On 22.02.2010 19:11, Achim Hoffmann wrote:
>
> Simple question about the *dates" in this draft:
>
> 1) If I understand 5.1.1. Dates correctly, the format of the date is
>     fixed and must be in GMT.
>     IIRC the date format in RFC2616 allows more variants. Also the timezone
>     may be different to GMT (see RFC2616, 19.3).

a) It requires recipients to accept certain obsolete formats, but also 
requires senders to use only rfc1123-date format.

b) What you see in 19.3 aren't requirements, but recommendations for 
handling invalid dates. The requirements are in Section 3.3 which says:

"All HTTP date/time stamps MUST be represented in Greenwich Mean Time 
(GMT), without exception."

> ...

BR, Julian