Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upMapped URI parameters should be implicitly decoded / unquoted #511
Comments
jamesls
added
the
documentation
label
Sep 1, 2017
This comment has been minimized.
This comment has been minimized.
|
Yes, thanks for reporting. We'll get that updated. |
This comment has been minimized.
This comment has been minimized.
|
@jamesls Thanks for the quick response.
and thinking it could be changed to something like this:
|
This comment has been minimized.
This comment has been minimized.
|
The tricky part here is because we're past the 1.0 release we have to maintain backwards compatibility, given people already have to unquote these params themselves so if we start to do that for them we may break users. I'd be interested in alternatives that could still preserve backwards compatibility. |
This comment has been minimized.
This comment has been minimized.
|
@jamesls I agree that it's best to preserve existing behavior (at least until the next major release). |


jstell commentedSep 1, 2017
•
edited
Maybe I'm missing something, but shouldn't mapped parameter values be implicitly decoded?
For example, if I'm looking for what state Los Angeles is in, I will do a
GET /cities/Los%20Angeles. The above handler will not give me the expected answer, because it doesn't unquoteLos%20Angelesback toLos Angeles.Shouldn't there be a call to do
city = urllib.unquote_plus(request.query_params['city'])?