W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2012

RE: Managing Obsolete Information

From: Joe Mason <jmason@rim.com>
Date: Wed, 5 Sep 2012 17:19:16 +0000
To: Karl Dubost <karld@opera.com>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
Message-ID: <2A6A8E813F7F9E43ADED124587F637CA07749114@XMB116CNC.rim.net>
> From: Karl Dubost [karld@opera.com]
>
> I'm not sure if there is a right solution and maybe it's fine as it is. I 
> would imagine sometimes a code in 2xx series could be sent back ala
> 
> 2xx Obsolete or 2xx Archived
> 
> It is different from Gone. It just says the information at this URI is here we
>  can give it to you but note that it is not meant as something fresh. The 
> clients coming to the site know their goals such as archiving bots for 
> example. Some bots which are more focused on the new new shining things might 
> decide to ignore this URI because it is obsolete and prefer to spend time 
> indexing good fresh stuff. Bookmarks of people fond of old stuff will still be
>  working.
> 
> Note that there could be even a Location: sent along with the new fresh stuff 
> is there. You may decide to go or stay here.

I think this would be better as a 3xx code.  (3xx Supplanted, perhaps - I was going to say Superseded but it's too hard to spell.) 

Joe
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Wednesday, 5 September 2012 17:19:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 5 September 2012 17:19:53 GMT