Re: cache-busting document
Drazen Kacar (dave@srce.hr)
Sat, 7 Jun 1997 18:59:34 +0200
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
acceptable.
--
.-. .-. Life is a sexually transmitted disease.
(_ \ / _)
| dave@srce.hr
| dave@fly.cc.fer.hr