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

RE: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST

From: Brian Smith <brian@briansmith.org>
Date: Tue, 29 Jul 2008 14:29:15 -0500
To: "'Mark Baker'" <distobj@acm.org>, "'Julian Reschke'" <julian.reschke@gmx.de>
Cc: "'Mark Nottingham'" <mnot@mnot.net>, "'HTTP Working Group'" <ietf-http-wg@w3.org>
Message-ID: <DBDF6622E5E24DC8A0DBD9DA4F988B74@T60>

Mark Baker wrote:
> On Tue, Jul 29, 2008 at 2:02 PM, Julian Reschke 
> <julian.reschke@gmx.de> wrote:
> > So, for instance for PUT, servers are expected to store it 
> > and return them in a subsequent GET?
> 
> That's up to the server.  From an HTTP POV, the meaning of 
> both request and response messages containing a 
> Content-Location header seems unambiguous.

It causes problems because Content-Location determines the base URI for
relative URI references in a response. If it means anything in a *request*
then I expect it would retain this base-URI functionality there too. But, a
server cannot echo the Content-Location as the client sent it (because it
may be a URI on a totally unrelated server), and it can't be expected to
find and rewrite all the URI references in the request entity before
republishing it. Saying that Content-Location is undefined in requests is
important because that statement indicates to client software authors that
they cannot rely on using this header as the base URI when submitting
documents to servers; they need to use xml:base or similar mechanisms.

- Brian
Received on Tuesday, 29 July 2008 19:29:50 GMT

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