[issue16679] Wrong URL path decoding
Claude Paroz
report at bugs.python.org
Fri Dec 14 11:47:22 CET 2012
Claude Paroz added the comment:
I may understand your reasoning when you cannot make any assumptions about the encoding of a series of bytes.
I think that the case of PATH_INFO is different, because it should comply with standards, and then you *can* make the assumption that the original path is 'utf-8'-encoded. So either leave the string undecoded, or decode it to what the standards say. It would put un unneccessary burden on WSGI apps to always require to encode-redecode this string.
Wouldn't it be possible to amend PEP 3333?
Hopefully we can get some other opinions about this issue.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16679>
_______________________________________
More information about the Python-bugs-list
mailing list