W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2006

Re: NEW ISSUE: Drop Content-Location

From: Henrik Nordstrom <hno@squid-cache.org>
Date: Thu, 30 Nov 2006 00:12:24 +0100
To: "Yngve N. Pettersen (Developer Opera Software ASA)" <yngve@opera.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, Anne van Kesteren <annevk@opera.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1164841944.15658.81.camel@henriknordstrom.net>
ons 2006-11-29 klockan 23:54 +0100 skrev Yngve N. Pettersen (Developer
Opera Software ASA):

> Short story: Given the incorrect usage we have seen in the past few years  
> it is not possible to implement client side support of Content-Location as  
> a Base URL replacement. If such functionality is desired, an entirely new  
> header must be defined.

I don't share this view. Adding new names for an existing header is not
a solution to the problem of people not following specifications.

The only way forward it to gradually collectively work towards getting
Content-Location understood. It's not an impossible war, it's about
educating the site/server owners/designers about the HTTP protocol and
why doing things the wrong way is hurting themselves in the long run.

This war has already been fought with the Vary header, and things has
improved considerably over the years to the point that today you can
almost trust Vary. That war is now moving forward to also raise the
level of understanding of ETag.

It will take time and some energy, but is not impossible. A large part
is to identify the actual sources of the errors, then to try to ensure
that there is some efforts taken in reducing the knowledge gap.


Received on Wednesday, 29 November 2006 23:13:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 9 September 2019 17:47:10 UTC