- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 10 Mar 2010 11:27:39 -0500
- To: Julian Reschke <julian.reschke@gmx.de>
- CC: HTTP Working Group <ietf-http-wg@w3.org>, "public-html@w3.org" <public-html@w3.org>
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. -Boris
Received on Wednesday, 10 March 2010 16:28:24 UTC