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: Wed, 10 Mar 2010 17:32:37 +0100
• To: Boris Zbarsky <bzbarsky@MIT.EDU>
• CC: HTTP Working Group <ietf-http-wg@w3.org>, "public-html@w3.org" <public-html@w3.org>
• Message-ID: <4B97C9A5.2030803@gmx.de>

On 10.03.2010 17:27, Boris Zbarsky wrote:
> On 3/10/10 8:06 AM, Julian Reschke wrote:
>> the HTTPbis WG has two open tickets with respect to the syntax and
>> semantics of the Location header (not to be confused with
>> Content-Location!):
>
> As long as you're doing this, can you please define the behavior for
> non-ASCII values of the header? At the moment the header only allows
> URIs, with non-ASCII bytes having undefined behavior. UAs treat this
> inconsistently (some treat the bytes as UTF-8, some URI-escape all
> non-ASCII bytes; there may be other behaviors). This particularly comes
> up with IDN hostnames and URL minifiers which just stick the non-ASCII
> hostname into their Location header.

Again:

 > (*) We'll look at *that* issue separately.

BR, Julian

Received on Wednesday, 10 March 2010 16:33:17 UTC