- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Mon, 24 Mar 2014 17:03:24 +0900
- To: Bjoern Hoehrmann <derhoermi@gmx.net>, Zhong Yu <zhong.j.yu@gmail.com>
- CC: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 2014/03/22 01:04, Bjoern Hoehrmann wrote: > * Zhong Yu 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. > > The same is often also true for the query part if it doesn't come from a > form submission the browser controlled. Hence my question to Nicolas, > <http://lists.w3.org/Archives/Public/ietf-http-wg/2014JanMar/1145.html>. If the draft gets anywhere, it has to say very clearly that the header field(s) must only be used when the encoding is actually known. So input from the address field, form input, and in-browser conversion of IRIs to URIs are okay, but adding header fields for URIs that are already %-encoded is not. Regards, Martin.
Received on Monday, 24 March 2014 08:03:58 UTC