cache-busting and charsets again
W.Sylwestrzak@icm.edu.pl ("W.Sylwestrzak@icm.edu.pl")
Wed, 11 Jun 1997 04:29:14 +0200 (MET DST)
I wrote:
>
> > Unfortunately most of the servers practicing this today
> > try to perform a 'naive' content negotiation, which effectively
> > uses redirects to other urls. This is of course wrong,
> > because it unnecessarily expands the url addressing space,
> > thus making caching less effective.
Drazen Kacar:
> It isn't, because you'll suffer one redirection, but the target is
> cacheable. Compare it to serving different variants right away with
> ensuring that it won't be cacheable if the client is HTTP/1.0 compliant.
I never claimed it's not cacheable. All I say is that this unnecessarily
multiplies the number of cached objects, which is bad.
--w