I unfortunately couldn't find anything in the WSGI spec to indicate whether or not I could expect environ variables relating to the URL to be URL decoded when I get them or whether they reflect the raw URL that was sent to the browser.

This recently became an issue, when a user noticed that the %2B URL encoding for a + sign, had turned into a space when it hit their app. Sure enough, Paste was doing URL un-quoting, then Routes, and the double URL un-quote resulted in the + being a space.

Is there some definitive word on whether a WSGI application should expect to have it URL un-quoted or not?

Cheers,
Ben

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe: 
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com

Reply via email to