W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1995

Re: Improving If-Modified-Since

From: Lou Montulli <montulli@mozilla.com>
Date: Tue, 15 Aug 95 13:00:37 -0700
Message-Id: <3030FCE5.41C6@mozilla.com>
To: Roy Fielding <fielding@beach.w3.org>
Cc: Lou Montulli <montulli@mozilla.com>, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
> At the same time, we can specify that IMS may contain additional
> parameters for each of the Content-* headers that are applicable,
> and the server may also use those for determining the correct response.
> That means "length" instead of "size" -- there's no sense in using a
> different name for the same thing.

length sounds good.  It's two more bytes but it is more consistant.

> 
> NOTE:  The reason you have been getting lots of bug reports due
> to corrupted or out of date caches is because of a bug in Navigator.
> When the user requests a "Reload" of a URL, the user agent should add
> 
>    Proxy: no-cache
> 
> and must not include an If-Modified-Since header.  Navigator 1.1N sends
> the no-cache directive, but also sends IMS.  Fix that and you won't get
> any more bug reports about cache corruption problems, since the user
> will be in control of their cache.

Actually it's called "Pragma: no-cache", and Netscape has always sent this
for reloads.

:lou
-- 
Lou Montulli                 http://www.mcom.com/people/montulli/
       Netscape Communications Corp.
Received on Tuesday, 15 August 1995 13:03:20 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:31:24 EDT