Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wsgi-intercept does not urldecode PATH_INFO #12

Open
GoogleCodeExporter opened this issue Dec 4, 2015 · 1 comment
Open

wsgi-intercept does not urldecode PATH_INFO #12

GoogleCodeExporter opened this issue Dec 4, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

This seems to be inconsistent with the WSGI spec. However it has been 
pointed out that this default behaviour creates problem for some cases. 
(http://code.google.com/p/wsgi-intercept/issues/detail?id=11) It would be 
really swell if there could be a configuration flag that would turn the 
url decoding on/off.

Thanks. 

Original issue reported on code.google.com by [email protected] on 22 Sep 2008 at 3:21

@GoogleCodeExporter
Copy link
Author

Note to self: For reference on the spec (I think it's the CGI spec that talks 
about
PATH_INFO), see 
http://mail.python.org/pipermail/web-sig/2008-January/003122.html . 
There was also a message in the twill list about how QUERY_STRING should not be
decoded: http://lists.idyll.org/pipermail/twill/2008-April/000875.html

Original comment by kumar.mcmillan on 22 Sep 2008 at 3:31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant