Re: #290: Motivate one-year limit for Expires

Mark Nottingham <mnot@mnot.net> Sun, 24 July 2011 18:18 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96FB321F8A69 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 24 Jul 2011 11:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YfmbCGhxRWMi for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 24 Jul 2011 11:18:33 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 1146921F8A64 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 24 Jul 2011 11:18:33 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Ql3Fv-0006Eo-5x for ietf-http-wg-dist@listhub.w3.org; Sun, 24 Jul 2011 18:18:23 +0000
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <mnot@mnot.net>) id 1Ql3Fo-0006Dt-Dy for ietf-http-wg@listhub.w3.org; Sun, 24 Jul 2011 18:18:16 +0000
Received: from mxout-07.mxes.net ([216.86.168.182]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1Ql3Fn-0006DA-Q6 for ietf-http-wg@w3.org; Sun, 24 Jul 2011 18:18:16 +0000
Received: from dhcp-1790.meeting.ietf.org (unknown [130.129.23.144]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 0D04622E247; Sun, 24 Jul 2011 14:17:54 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAAbTgTsXrNsx1jYwsAjMAbwxUFaHySfPmGqxJgzpfjOMxgiUAQ@mail.gmail.com>
Date: Sun, 24 Jul 2011 14:17:53 -0400
Cc: Willy Tarreau <w@1wt.eu>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A55312F4-F25B-407F-A0DD-F5D0B4F36A89@mnot.net>
References: <891657B9-2F11-43D6-A9A0-4C6663DAC127@mnot.net> <20110724175303.GU22405@1wt.eu> <CAAbTgTsXrNsx1jYwsAjMAbwxUFaHySfPmGqxJgzpfjOMxgiUAQ@mail.gmail.com>
To: Brian Pane <brianp@brianp.net>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-1.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1Ql3Fn-0006DA-Q6 187ff71fac8fc7602e586cb84cb61c05
X-Original-To: ietf-http-wg@w3.org
Subject: Re: #290: Motivate one-year limit for Expires
Archived-At: <http://www.w3.org/mid/A55312F4-F25B-407F-A0DD-F5D0B4F36A89@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/11058
X-Loop: ietf-http-wg@w3.org
Sender: ietf-http-wg-request@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Resent-Message-Id: <E1Ql3Fv-0006Eo-5x@frink.w3.org>
Resent-Date: Sun, 24 Jul 2011 18:18:23 +0000

On 24/07/2011, at 2:16 PM, Brian Pane wrote:

> I think the problem with ignoring on the client side is that the
> clients that would need to ignore large values the most are probably
> those least likely to detect the problem.  E.g, if you send this:
> 
>    Expires: Fri, 01 Jan 2100 00:00:01 GMT
> 
> to a client that uses 32-bit Unix time_t values to hold times, how
> will that client interpret it?  The implementation might be able to
> detect the overflow, but maybe not.


Right -- to me, that's a bigger concern, and we might amend the proposed text to note that specifically. I don't know that we can do much else; implementations are just going to have to change how they store and work with time as it approaches...

Cheers,

--
Mark Nottingham   http://www.mnot.net/