This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26398 - application/x-www-form-urlencoded serializer overly precent-encoding?
Summary: application/x-www-form-urlencoded serializer overly precent-encoding?
Status: RESOLVED MOVED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: URL (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+urlspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-21 14:04 UTC by Simon Sapin
Modified: 2015-08-14 16:56 UTC (History)
3 users (show)

See Also:

Attachments

Description Simon Sapin 2014-07-21 14:04:15 UTC 
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?
Comment 1 Anne 2014-07-27 11:24:35 UTC 
Are you saying existing implementations are not following the specification?
Comment 2 Simon Sapin 2014-07-27 12:13:36 UTC 
Right, I forgot to leave my sense of logic art the door. I'll do some testing.
Comment 3 Anne 2015-06-15 16:36:14 UTC 
I think ideally we align this with the query state from the URL parser.
Comment 4 Anne 2015-08-14 13:14:58 UTC 
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.)
Comment 5 Anne 2015-08-14 16:56:17 UTC 
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.