W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 1998

Re: Multiple Content-Location headers

From: Ben Laurie <ben@algroup.co.uk>
Date: Wed, 14 Jan 1998 00:33:49 +0000
Message-Id: <34BC07ED.A9C96FEC@algroup.co.uk>
To: "David W. Morris" <dwm@xpasc.com>
Cc: Jacob Palme <jpalme@dsv.su.se>, Scott Lawrence <lawrence@agranat.com>, IETF working group on HTML in e-mail <mhtml@segate.sunet.se>, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/5168
David W. Morris wrote:
> On Tue, 13 Jan 1998, Jacob Palme wrote:
> > At 08.52 -0500 98-01-13, Scott Lawrence wrote:
> > > The usage of Content-Location within HTTP is specifically to allow the
> > > specification of which one of some number of alternate versions of an
> > > entity is in this response.
> >
> > I do not quite understand how you are able to designate one location
> > as the primary one, if you are sending two copies of exactly the
> > same object, referenced in two different ways. In the case you
> > describe, how can you say that C is primary and D is secondary?
> The point is that a single resource may exist in english and french
> versions (or an image in high, medium, and low resolution, etc.) and
> based on other information, primarily HTTP header content such as
> Accept-language, the server picks one of the versions to return as the
> response. The server notifies the client and any intervening caches
> that the identity of the response is some other URL via the
> Content-location field. In other words, the versions are not the
> exact same object.

Eh? Aren't you describing variants here?



Ben Laurie            |Phone: +44 (181) 735 0686|Apache Group member
Freelance Consultant  |Fax:   +44 (181) 735 0689|http://www.apache.org
and Technical Director|Email: ben@algroup.co.uk |Apache-SSL author
A.L. Digital Ltd,     |http://www.algroup.co.uk/Apache-SSL
London, England.      |"Apache: TDG" http://www.ora.com/catalog/apache
Received on Tuesday, 13 January 1998 16:38:22 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:04 UTC