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: Mon, 9 Jun 1997 01:16:55 +0200
Message-Id: <19970609011655.03471@jagor.srce.hr>
To: W.Sylwestrzak@icm.edu.pl
Cc: "David W. Morris" <dwm@xpasc.com>, dave@srce.hr, martin@mrrl.lut.ac.uk, http-wg@cuckoo.hpl.hp.com, ircache@nlanr.net
Wojtek Sylwestrzak 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.

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.

> Most of the contemporary clients are able to convert
> character encoding on the fly, so that the rendered document
> is presented to the reader with the font sets locally available.

First, many people use old software. Second, if the right font is not
locally available, most of your contemporary clients will produce
garbage.

-- 
 .-.   .-.    Life is a sexually transmitted disease.
(_  \ /  _)
     |        dave@srce.hr
     |        dave@fly.cc.fer.hr
Received on Sunday, 8 June 1997 16:18:46 EDT

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