- From: Henrik Nordstrom <henrik@henriknordstrom.net>
- Date: Thu, 07 Aug 2008 16:31:56 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Stefan Eissing <stefan.eissing@greenbytes.de>, HTTP Working Group <ietf-http-wg@w3.org>
ons 2008-08-06 klockan 15:42 +0200 skrev Julian Reschke: > Stefan Eissing wrote: > > Is there a need to express the client's expectation that the > > "Content-Location" URL will only have a single entity associated with > > it? Or is a client expected to follow "Content-Location"s for a number > > of times? > > I wouldn't want to encourage that case, but would anything break if that > happened? The cache model of HTTP assumes that Content-Location is unique per variant of the request-URI, which kind of implies that the Content-Location URI is not a negotiated resource. For each Request-URI Content-Location has the same uniqueness requirement across the variants (but not versions) as ETag. ETag is also version unique.. And when Content-Location is placed in the original HTTP content model then it's very clear.. Content-Location is a direct unique reference URI to a specific resource object with no negotiation or transformation. Regards Henrik
Received on Thursday, 7 August 2008 14:30:59 UTC