If I can get the formatting to work here... the simplest example would be: /foo/element%2Ftwo/bar this three element path ought to be easily parsed and ro

If I can get the formatting to work here... the simplest example would be: /foo/element%2Ftwo/bar this three element path ought to be easily parsed and routed to a handler for "foo" that can have two args which would receive the path elements: element%2Ftwo bar in other words, one path element has a quoted slash in it. But instead, it gets unquoted at the WSGI layer into: /foo/element/two/bar and then such routing would fail entirely or get the arguments wrongly chopped up, depending on how routing patterns work in the framework. This same problem applies to all the "reserved" chars from the spec, e.g. slashes, semi-colons, colons, equal-sign, asterisk, parentheses, and more.