- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 24 Mar 2014 09:01:04 +0100
- To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Zhong Yu <zhong.j.yu@gmail.com>, Bjoern Hoehrmann <derhoermi@gmx.net>
- CC: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 2014-03-24 08:53, "Martin J. Dürst" wrote: > ... >> But the browser has no idea how the URI path was constructed, it would >> be presumptuous for the browser to brave a guess and mislead the >> intermediaries. > > Björn described the situation from a server point of view. From a client > point of view, the client just encodes the path part of an URI/IRI with > UTF-8, and the query part with the encoding of the page. That's a bit misleading. The client doesn't encode the path at all, unless it *requires* encoding. That is, if I have "/path%A0" in a href attribute, this is what will get on the wire. > ... Best regards, Julian
Received on Monday, 24 March 2014 08:02:31 UTC