[Web-SIG] WSGI 2.0 Round 2: requirements and call for interest

Graham Dumpleton graham.dumpleton at gmail.com
Tue Jan 5 17:37:34 EST 2016

> On 6 Jan 2016, at 9:19 AM, Graham Dumpleton <graham.dumpleton at gmail.com> wrote:
>> On 6 Jan 2016, at 12:09 AM, chris.dent at gmail.com <mailto:chris.dent at gmail.com> wrote:
>> As someone who writes their WSGI applications as functions that take
>> `start_response` and `environ` and doesn't bother with much
>> framework the things I would like to see in a minor revision to WSGI
>> are:
>> * A consistent way to access the raw un-decoded request URI. This is
>>  so I can reconstruct a realistic `PATH_INFO` that has not been
>>  subjected to destructive handling by the server (e.g. apache
>>  messing with `%2F`) before continuing on to a route dispatcher.
> This is already available in some servers by way of the REQUEST_URI value.
> This is the original first line of any HTTP request and can be split apart to get the path.

Whoops. My foggy memory. REQUEST_URI is only raw path part, not the whole request line with method, protocol and path.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/web-sig/attachments/20160106/757d69ac/attachment-0001.html>

More information about the Web-SIG mailing list