Re: Extending redirects to suggest updated locations ?

On 03.10.2010 08:01, Willy Tarreau wrote:
> ...
> 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.
> ...

Yes.

> ..
> 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 ?

How about:

HTTP/1.1 200 OK
Content-status: deprecated
Link: <haproxy-1.4.9.tar.gz>; rel=newest-version

?

Best regards, Julian