W3C home > Mailing lists > Public > www-tag@w3.org > August 2007

Re: ISSUE-57: The use of HTTP Redirection

From: Alan Ruttenberg <alanruttenberg@gmail.com>
Date: Fri, 24 Aug 2007 00:57:34 -0400
Message-Id: <CECEC8AD-CB52-4458-ABC8-B488615B164A@gmail.com>
To: Technical Architecture Group WG <www-tag@w3.org>

Would it be possible to add to the agenda something more about  
predictability of what the redirection is to (e.g., when can I expect  
rdf?) and the ability to specify a relation of the redirected-to  
resource to the original more specific than, effectively, "seeAlso".

Thank you,
Alan Ruttenberg

On Aug 22, 2007, at 5:10 AM, Technical Architecture Group Issue  
Tracker wrote:

>
> ISSUE-57: The use of HTTP Redirection
>
> http://www.w3.org/2001/tag/group/track/issues/
>
> Raised by: Stuart Williams
> On product:
>
> At their meeting in 16th July 2007 [1] the TAG resolved to create a  
> new issue, HttpRedirections-57 as a response to a community request  
> [2] that we give further consideration to the use of the HTTP 303  
> status codes *and* other possible mechanisms of obtaining a  
> description of a resource (typically a non-information resource)  
> where the referenced resource is not capable of providing  
> representations of itself.
>
> Particular concerns are the cachability (or otherwise) of HTTP  
> redirection responses (see email from Roy Fielding [3] indicating  
> presense of a bug in the specs); UI confusion where redirection  
> leds to changes in browser address-bar content and questions of the  
> practical bookmarkability of a reference in the presence of a  
> redirections.
>
> Stuart Williams
> For W3C TAG
> --
> [1] http://www.w3.org/2001/tag/2007/07/16-minutes#item06
> [2] http://lists.w3.org/Archives/Public/www-tag/2007Jul/0034
> [3] http://lists.w3.org/Archives/Public/www-tag/2007Jul/0035
>
>
>
>
Received on Friday, 24 August 2007 04:57:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:47 GMT