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

Re: cache-busting document

From: Drazen Kacar <dave@srce.hr>
Date: Sat, 7 Jun 1997 18:59:34 +0200
Message-Id: <19970607185934.59591@jagor.srce.hr>
To: Martin Hamilton <martin@mrrl.lut.ac.uk>
Cc: http-wg@cuckoo.hpl.hp.com, ircache@nlanr.net
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/3438
Martin Hamilton wrote:

>   Don't parse USER_AGENT to switch on browser capabilities, since
>     the cached HTML will be browser specific.  Use features like
>     <NOFRAMES> instead.

Why not? If I make a redirect, it will be cacheable. Besides, NOFRAMES tag
doesn't have any purpose. It's a wrong example.

>   Don't use redirects, since their results are uncacheable.

301 is cacheable, 302 is not. Use what you need.

>   Don't use content-negotiation until HTTP 1.1 is more widely
>     deployed, since in HTTP/1.0 it interacts badly with proxy caches.

What am I supposed to use until then?

>   Don't use server modules or scripts to convert document's character
>     set on the server side.  Leave it to the client.

What if the client can't do it? The text will be unreadable. That's not

 .-.   .-.    Life is a sexually transmitted disease.
(_  \ /  _)
     |        dave@srce.hr
     |        dave@fly.cc.fer.hr
Received on Saturday, 7 June 1997 10:05:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:20 UTC