Re: #375: Most Conservative (caching and date parsing)

On 16/07/2012 6:28 p.m., Mark Nottingham wrote:
> <>
>> If an HTTP header field incorrectly carries a date value with a time zone other than GMT, it must be converted into GMT using the most conservative possible conversion.
> What does "most conservative" mean?
> "Earliest" makes sense for Expires and Date, but Last-Modified it would seem that "latest" is the most conservative.

Precisely. Is any different view of "conservative" possible?

> I really don't want to create a registry -- or even another aspect that each header has to define -- here.
> Maybe just a few examples would help?

Or moving the error recovery into the header definitions with 
appropriate differences? As you note there is no one fix that fits all 
date usages.


Received on Monday, 16 July 2012 08:46:10 UTC