- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 8 Oct 2009 09:39:09 +1100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>, Ian Hickson <ian@hixie.ch>, Anne van Kesteren <annevk@opera.com>, Roy Fielding <fielding@gbiv.com>
On 08/10/2009, at 12:31 AM, Julian Reschke wrote: > Mark Nottingham wrote: >> I haven't seen any discussion of this, but I believe the general >> feeling is to drop the base-setting semantics of Content-Location >> in HTTP. >> Any other thoughts? Otherwise we'll go in that direction. > > +1, but we need to consider the details. > > Currently, we have > > "The value of Content-Location also defines the base URI for the > entity." > > Do we drop this (potentially breaking currently conforming > implementations), or do we make it optional? Personally, I'd say the former; we've found cases where it can be harmful, it isn't widely implemented, and making it optional will lead to yet more interoperability problems. We are chartered to improve interop, and are explicitly allowed to change things when this is the case. > In both case, we'll also have to record this as a normative change > in the Changes section. Yes. -- Mark Nottingham http://www.mnot.net/
Received on Wednesday, 7 October 2009 22:39:47 UTC