Date in If-modified-since header

I have been brought up the issue of the date string used in the
If-modified-since header.  Current practice is to use the
Last-modified header, and given clock skew, it's also the only
foolproof way to do IMS requests.  Could the wording in the spec be
changed to reflect that, and eliminate this source of data
incorrectness?  Basically, change the semantics of "If-modified-since"
be "In-not-equal-last-modified".

Netscape servers and proxy were changed to use an equality check,
because there were cases, with older software, incorrectly set
timezones or machine times and daylight savings times where the dates
would be off and stale data would be rendered up-to-date.

Ari Luotonen	* * * Opinions my own, not Netscape's * * *
Netscape Communications Corp.
501 East Middlefield Road
Mountain View, CA 94043, USA		Netscape Proxy Server Development

Received on Tuesday, 15 October 1996 13:46:53 UTC