Ben Bangert wrote: > 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?
The last time I asked that question here [1], Phillip kindly pointed out to me that that's defined by the CGI spec. I could go through the agony of distributed English-obfuscated BNF analysis again, but I'll just note that I changed CP's wsgiserver to do decoding that very day. So I think the answer is "yes". Robert Brewer [EMAIL PROTECTED] [1] http://mail.python.org/pipermail/web-sig/2006-August/002230.html _______________________________________________ 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
