cache-busting and charsets again

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

Received on Tuesday, 10 June 1997 19:31:14 UTC