- From: Ian Hickson <ian@hixie.ch>
- Date: Fri, 13 Aug 2004 14:04:43 +0000 (UTC)
On Tue, 13 Jul 2004, fantasai wrote: > > > > > > > > > > # Handle as if enctype was application/x-www-form-urlencoded > > > ... > > > The text for "application/x-www-form-urlencoded" says > > > # Use the encoded data set as the query value for a URI formed > > > # from the action URI and fetch it via HTTP GET. > > > > > > For x-www-form-urlencoded, the URL-escaping happens during the > > > encoding stage. Therefore the encoded data set is already escaped, > > > and can just be appended as the query value. > > > > If you are handling the submission as if the enctype was > > application/x-www-form-urlencoded, then why would you encode the data set > > using application/x-www-form+xml? The whole _point_ is that you use > > application/x-www-form-urlencoded! > > Woah. I so *totally* did not get that. Where does it say you re-encode > it before doing the protocol-submission thing? Where does it say that you encode it using the wrong type in the first place? I don't get it. > (For all the other fields, you say "Use the encoded data set", which to > me means that you've got the stuff already encoded. Encoding is even > specified in the previous section with no caveats about weird stuff > happening based on the submission behavior matrices.) I suppose I can make it more explicit. I added the second sentence to this note before the tables: <p class="note">In the tables below, cells that specify that the case should be handled as another represent cases where the given attribute combinations are otherwise meaningless. In such cases, the encoded data set is created from the fallback encoding type, not the specified encoding type.</p> -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 13 August 2004 07:04:43 UTC