W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2007

Re: NEW ISSUE: Content-Location vs PUT/POST

From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Tue, 31 Jul 2007 21:04:46 +0200
To: Julian Reschke <julian.reschke@gmx.de>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1185908686.29279.16.camel@henriknordstrom.net>
On tis, 2007-07-31 at 20:48 +0200, Julian Reschke wrote:

> Can you define "mismatch" here? When a client says "here's another 
> Content location for the entity I'm sending", how can the server dtect a 
> mismatch? (well, except for fetching the entity and comparing?)

For a server doing raw PUT:

If Content-Location differs from the Request-URI, or different from the
intended store location when the Request-URI is a negotiated resource.


For a server processing the PUT entity and not storing the
Content-Location:

If the entity can not be processed in such manner that any references in
it makes sense at it's stored location, compared to the
Content-Location.


Regards
Henrik

Received on Tuesday, 31 July 2007 19:05:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:15 GMT