Re: [http-state] IETF-wide Last Call for -httpstate-cookie-10 ?

Daniel Stenberg <daniel@haxx.se> Wed, 01 September 2010 20:30 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 183DF3A6904 for <http-state@core3.amsl.com>; Wed, 1 Sep 2010 13:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.82
X-Spam-Level:
X-Spam-Status: No, score=-2.82 tagged_above=-999 required=5 tests=[AWL=-1.171, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_73=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 0ctdMbgJ9Myt for <http-state@core3.amsl.com>; Wed, 1 Sep 2010 13:30:19 -0700 (PDT)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id EDDF33A685A for <http-state@ietf.org>; Wed, 1 Sep 2010 13:30:18 -0700 (PDT)
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 o81KUork029927; Wed, 1 Sep 2010 22:30:50 +0200
Date: Wed, 1 Sep 2010 22:30:50 +0200 (CEST)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <4C7EAB2F.6050007@stpeter.im>
Message-ID: <alpine.DEB.2.00.1009012203530.7470@tvnag.unkk.fr>
References: <4C759235.6010000@KingsMountain.com> <5l7g76hcdhobfsd4nrilfhuvth42br7sjf@hive.bjoern.hoehrmann.de> <AANLkTikFsb0v5h-PszE1jgtrUk1str9vo+4gzQ9CTug=@mail.gmail.com> <fddg76t5nqdn28a2ft639i6a6k51um2stg@hive.bjoern.hoehrmann.de> <4C7EAB2F.6050007@stpeter.im>
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
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.3.5 (giant.haxx.se [80.67.6.50]); Wed, 01 Sep 2010 22:30:50 +0200 (CEST)
Cc: HTTP-state mailing list <http-state@ietf.org>
Subject: Re: [http-state] IETF-wide Last Call for -httpstate-cookie-10 ?
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, 01 Sep 2010 20:30:22 -0000

On Wed, 1 Sep 2010, Peter Saint-Andre wrote:

> If the date processing behavior of existing implementations is an open 
> issue, then perhaps the WG can settle on the correct wording via list 
> discussion, or add the issue to the tracker:

I setup a little CGI that can be used to check what your browser thinks:

 	http://daniel.haxx.se/cookie.cgi

It sends a single cookie header that looks like:

 	"Set-Cookie: testme=yesyes; expires=Wed Sep  1 22:01:55 69;"

The script prints the Cookie: headers, so if you reload you should see 
"testme=yesyes" being output if the cookie is still there. If the cookie is 
still there, your browser of choice treats the date above as a date in the 
future.

My friends and I did a quick round and we tested a few browsers:

Future:

   Firefox (2069)
   curl (2147483647 seconds)
   IE 7 (2069)
   Opera (year 2036)
   Android

Historic:

   Chrome (both v4 and v5)

Conclusion:

Most clients seem to agree that '69' refers to '2069'.

-- 

  / daniel.haxx.se