- From: Zhong Yu <zhong.j.yu@gmail.com>
- Date: Fri, 21 Mar 2014 11:00:59 -0500
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
On Fri, Mar 21, 2014 at 10:53 AM, Julian Reschke <julian.reschke@gmx.de> wrote: > On 2014-03-21 16:36, Zhong Yu wrote: >> >> ... >> >> 2. If a browser submits a POST form with >> enctype=application/x-www-form-urlencoded, it may declare the >> character encoding used for the request entity body. But we'll need a >> better header name than "URI-Query-Encoding". Note that we cannot add >> a "charset=" parameter to the Content-Type header for this purpose - >> servers are not expecting it; they do not need it; they may be broken >> because of it. >> ... > > > See > <http://www.w3.org/TR/html5/forms.html#application/x-www-form-urlencoded-encoding-algorithm> > and look for "_charset_". Yes. The issue addressed by Gabriel's draft seems to be in the scope of HTML, not HTTP. And even if some kind of mechanism of declaring query encoding becomes official, any intermediary relying on it will have a bad time. > > Best regards, Julian
Received on Friday, 21 March 2014 16:01:26 UTC