- From: Daniel W. Connolly <connolly@beach.w3.org>
- Date: Wed, 20 Dec 1995 13:15:56 -0500
- To: David Robinson <drtr1@cus.cam.ac.uk>
- Cc: masinter@parc.xerox.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
In message <m0tSQLW-000DJMC@ursa.cus.cam.ac.uk>, David Robinson writes: >>... >>Most of the current proposals for headers back and forth don't handle >>this situation correctly. Yet a straight-forward enumeration of >>'depends-on' in the return from the server to the proxy, along with >>proxy services that preserve that information and also all headers >>that comprise the things the value returned depended upon, would be a >>good first step. For some headers, (accept, for example), you need >>more than merely knowing what it depended upon, but also the WAY in >>which it depended upon the original data, so that the proxy itself can >>decide whether a cached item is appropriate. > >Absolutely. A Vary: 1#(http-header-name) header returned by the server >would help solve this problem. I like this syntax. The URI header would work, but this is short and to the point. Dan
Received on Wednesday, 20 December 1995 10:20:34 UTC