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

Extending redirects to suggest updated locations ?

From: Willy Tarreau <w@1wt.eu>
Date: Sun, 3 Oct 2010 08:01:47 +0200
To: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20101003060147.GA3711@1wt.eu>

it recently happened to me again that some people downloaded an old
deprecated version of some software I authored, installed it in
production and blogged about it with links to the deprecated software.
The link is basically a link to the tgz, such as :


When the link points to an old version which contains at least 50
known bugs, then I'm sure that in the following days the support
mailing list will receive several mails reporting known issues. In
fact, knowing that users will experience issues sooner or later
worries me much more than to think they'll send mails about that.

I've already thought about replacing the file with a symlink to the
new version or to perform a redirect to the new version, but that's
really not friendly to admins or packagers who really need version
X or Y because they maintain it and apply the fixes on top of them.
And in general I don't like removing contents from the net, whether
it's buggy or not.

Thus I realized that we might be missing a possibly useful feature.
What is needed to cover the issue above would be either to have the
ability to report an "obsolete" or "deprecated" status to the user
agent for the file being downloaded, or to report a Location header
indicating where to get the newer version, or maybe both.

In both cases, the user agent would have two possibilities :
  - either it is automated (wget, curl, etc...) and wouldn't care
    about those headers. It could eventually log them if it provides
    a log of the downloads.

  - or it would be interactive and controlled by a user (browser), so
    it could report the status to the user and ask him if he still
    wants to download that content, or prefers to be redirected to the
    updated location (which may either be a page or downloadable contents).

Since the behaviour only depends on whether we're responding to a machine
or to a human being, I don't think it can easily be addressed on the server
side alone.

So, for instance, we could have :

HTTP/1.1 200 OK
Content-status: deprecated
Location: /download/1.4/src/haproxy-1.4.9.tar.gz
... + requested contents

Or perhaps :

HTTP/1.1 303 Found
Content-status: deprecated
Location: /download/1.4/src/haproxy-1.4.9.tar.gz
... + requested contents

Or maybe :

HTTP/1.1 200 OK
Content-status: deprecated; preferred=/download/1.4/src/haproxy-1.4.9.tar.gz
... + requested contents

I think the former would be better since it still allows server-side
intermediaries to rewrite paths as they do for many apps today.

Have I missed something ? Would it be useful to work on something like this,
and is it appropriate for the HTTP spec ?

Received on Sunday, 3 October 2010 06:02:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:55 UTC