- From: Zhong Yu <zhong.j.yu@gmail.com>
- Date: Fri, 21 Mar 2014 10:46:19 -0500
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- Cc: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
On Fri, Mar 21, 2014 at 10:42 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote: > * Zhong Yu wrote: >>1. It's improbable that the origin server uses separate encoding >>schemes for path and query. If the encoding scheme for the query part >>is known, it can be assumed for the path part too. > > This is actually a common situation. One reason is that the server > software handles the path, and some independent script handles the > query, and you might well have a server system that uses UTF-8 in > paths, but a legacy script expects ISO-8859-1 query strings. If it > is necessary and possible to communicate the encoding, if any, then > these two components need separate labels for maximum compatibility. Hmm, OK. 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. Zhong Yu > -- > Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de > Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de > 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Friday, 21 March 2014 15:46:54 UTC