➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients aclover, animus, claudep, docs@python, grahamd, martin.panter, pje
Date 2016-04-21.04:58:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461214690.42.0.395585643105.issue16679@psf.upfronthosting.co.za>
In-reply-to
Content 
PEP 3333 defers to a draft CGI specification for PATH_INFO and QUERY_STRING: <https://tools.ietf.org/html/draft-coar-cgi-v11-03>. (Dunno why it didn’t reference the final RFC 3875 instead, published 2004.) Anyway, both draft and final RFCs say “PATH_INFO is not URL-encoded”, but “the QUERY_STRING variable contains a URL-encoded search or parameter string”.

Graham, maybe you are seeing Latin-1 code points in PATH_INFO that have been translated from the %XX URL syntax, and QUERY_STRING retaining the original %XX syntax.
History
Date User Action Args
2016-04-21 04:58:10martin.pantersetrecipients: + martin.panter, pje, grahamd, aclover, docs@python, animus, claudep
2016-04-21 04:58:10martin.pantersetmessageid: <1461214690.42.0.395585643105.issue16679@psf.upfronthosting.co.za>
2016-04-21 04:58:10martin.panterlinkissue16679 messages
2016-04-21 04:58:10martin.pantercreate