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: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Thu, 31 Jul 2008 21:37:22 +0200
To: Brian Smith <brian@briansmith.org>
Cc: "'Julian Reschke'" <julian.reschke@gmx.de>, "'HTTP Working Group'" <ietf-http-wg@w3.org>
Message-Id: <1217533042.7595.12.camel@henriknordstrom.net>

On tor, 2008-07-31 at 08:36 -0500, Brian Smith wrote:
> Julian Reschke wrote:
> > Which means: it's ok to ignore Content-Location, if you "know" it.
> 
> I agree. Put another way, it is okay to remove or replace a Content-* header
> but you cannot ignore ones you don't understand.

And the reasons behind this is pretty simple. If you do not know what a
Content-* header means it's very likely you also do not know how to
handle the enclosed entity body in a sensible manner meaningful in PUT
context. Consider for example Content-Encoding where not understanding
the header and blindly ignoring it without considering the consequenses
will have quite dramatic effects on the end result. Similarly for most
other defined Content-* headers. (note: sniffing/guessing put aside
here..)

But in the end, how a server stores a resouce is an implementation
detail. Specs only care that the server can understand what it is
requested to store.

Regards
Henrik
Received on Thursday, 31 July 2008 19:38:06 GMT

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