26398 2014-07-21 14:04:15 +0000 application/x-www-form-urlencoded serializer overly precent-encoding? 2015-08-14 16:56:17 +0000 1 1 1 Unclassified WHATWG URL unspecified All All RESOLVED MOVED P2 normal Unsorted 1 simon.sapin annevk mike rubys simon.sapin sideshowbarker+urlspec oldest_to_newest 109132 0 simon.sapin 2014-07-21 14:04:15 +0000 Aside from the space/plus sign mapping, http://url.spec.whatwg.org/#concept-urlencoded-byte-serializer percent-encodes bytes corresponding to the following ASCII non-control characters: !"#$%&\'()+,/:;<=>?@[\]^`{|} This seems more than necessary. I believe these should be enough: "#&<=>` That is, those encoded in the URL parser’s query state, and &= which are the only significant characters in application/x-www-form-urlencoded. Is there a reason I’m missing? 109316 1 annevk 2014-07-27 11:24:35 +0000 Are you saying existing implementations are not following the specification? 109319 2 simon.sapin 2014-07-27 12:13:36 +0000 Right, I forgot to leave my sense of logic art the door. I'll do some testing. 121004 3 annevk 2015-06-15 16:36:14 +0000 I think ideally we align this with the query state from the URL parser. 122614 4 annevk 2015-08-14 13:14:58 +0000 But also, ideally we first make HTML use this algorithm rather than its own. (They're currently identical, I would not want them to get out of sync before we join them.) 122619 5 annevk 2015-08-14 16:56:17 +0000 I found that we also have https://github.com/whatwg/url/issues/18 and since GitHub is now preferred I'm going to mark this bug MOVED. Thank you for reporting this bug.