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

Re: draft-montenegro-httpbis-uri-encoding

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Fri, 21 Mar 2014 21:15:09 +1300
Message-ID: <532BF50D.3050200@treenet.co.nz>
To: ietf-http-wg@w3.org
On 21/03/2014 7:18 p.m., Mark Nottingham wrote:
> On 21 Mar 2014, at 4:43 pm, Amos Jeffries wrote:
>> What should servers (and intermediaries) receiving non-UTF-8 values in
>> these headers do when they rely on receiving UTF-8 URLs?
> I don't think it makes any difference to them; again, the URL on the wire is still ASCII, and that's still the cache key.

I have this nasty idea about client implementations starting to send
these headers with values indicating things like Unicode or Windows
charsets. That could lead to strange happenings in places like security
ACLs, background auth protocols, log processing software or TTY output
devices if the recipient intermediary was translating from url-encoding
to non-ASCII outputs.

Received on Friday, 21 March 2014 08:15:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:25 UTC