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

Daniel Stenberg <daniel@haxx.se> Wed, 01 September 2010 21:39 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 A6B343A684C for <http-state@core3.amsl.com>; Wed, 1 Sep 2010 14:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.061
X-Spam-Level:
X-Spam-Status: No, score=-3.061 tagged_above=-999 required=5 tests=[AWL=-0.812, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 qbFyiqjViPW3 for <http-state@core3.amsl.com>; Wed, 1 Sep 2010 14:39:17 -0700 (PDT)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id D58053A69AF for <http-state@ietf.org>; Wed, 1 Sep 2010 14:38:48 -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 o81Ld1tX012330; Wed, 1 Sep 2010 23:39:01 +0200
Date: Wed, 01 Sep 2010 23:39:01 +0200
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: =JeffH <Jeff.Hodges@KingsMountain.com>
In-Reply-To: <4C7EBDCA.7060003@KingsMountain.com>
Message-ID: <alpine.DEB.2.00.1009012311490.7470@tvnag.unkk.fr>
References: <4C7EBDCA.7060003@KingsMountain.com>
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 23:39:01 +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 21:39:19 -0000

On Wed, 1 Sep 2010, =JeffH wrote:

>>    curl (2147483647 seconds)
>
> huh, my calcs indicate 2147483647 (sec) ~= 68 (yr)  ?  If that then is 
> treated as "future", yet something else is going on (in curl) ?

Sorry, that was carelessly expressed. curl detects that the date is in the 
future, but as I ran it 32bit it cannot express that time in a time_t in 
seconds since 1970 so it stores the largest value it has for it. 2147483647 is 
68 years from 1970, so it becomes the year 2038.

> might you be able to tweak your .cgi script to test all year values from 0 
> <= year <= 100 such that we can see in detail what all happens to which year 
> values?

Great idea. I'll need to post those results in a separate post, as I'm trying 
to make sense from them. Stay tuned.

-- 

  / daniel.haxx.se