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

Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 11 Mar 2010 12:11:44 +0100
Message-ID: <4B98CFF0.7020901@gmx.de>
To: nrixham@gmail.com
CC: ietf-http-wg@w3.org
On 10.03.2010 19:12, Nathan Rixham wrote:
> Hi All,
>
>> 9.4.  Location
>> ...
>>      The field value consists of a single URI-reference.
>
> If the Location header is only used to:
>
>    1] identify a newly created resource
>    2] redirect the recipient to a different location
>
> doesn't this mean that:
>
>    location-field-value = absolute-URI
>                            / ( path-absolute [ "?" query ] )
>                            / ( relative-part [ "?" query ] )
>
> and fragments don't come in to the equation / should not be allowed?

Fragments in redirect targets are nothing new. They have been around 
since the beginning, and they are supported by UAs. And they can be useful.

> additionally how could a secondary resource (one identified by a
> uri-reference containing a fragment) be accurately redirected-to when
> secondary resources are not allowed in the request-target?

I have no idea what this has to do with the request-target. Could you 
please elaborate?

Best regards, Julian
Received on Thursday, 11 March 2010 11:12:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:17 GMT