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

Scheduling for -16.


On 30/07/2011, at 6:47 AM, Mark Nottingham wrote:

> Remove the requirement in p6 3.3 and replace it with:
> 
> """
> Historically, HTTP required the Expires field-value to be no more than a year in the future. While longer freshness lifetimes are no longer prohibited, extremely large values have been demonstrated to cause problems (e.g., clock overflows due to use of 32-bit integers for time values), and most caches will evict a response far sooner than that. Therefore, senders ought not produce them.
> """

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

Received on Thursday, 18 August 2011 04:18:37 UTC