Graham Dumpleton wrote:
> What is accepted convention for dealing with repeating slashes.
> Should any web server adapter leave repeating slashes in both
> SCRIPT_NAME and PATH_INFO, or should it at least normalise
> SCRIPT_NAME so that it matches the designated mount point.
The URI BNF allows for
Another question on SCRIPT_NAME, PATH_INFO etc.
This time I am after information on what responsibilities an adapter for a
specific web server has in respect of removal and/or preservation of repeating
slashes in a request URI.
Take for example that a WSGI application is mounted at:
/wsgi/a
a
At 07:07 PM 1/28/2007 +, Alan Kennedy wrote:
>[Graham Dumpleton]
> > Should a WSGI adapter for a web server which allows a mount point to
> > have a trailing slash specifically flag as a configuration error an
> > attempt to use such a mount point given that it appears to be
> > incompatible wi
Graham Dumpleton wrote:
> In the PEP it says:
>
> SCRIPT_NAME
>The initial portion of the request URL's "path" that corresponds
>to the application object, so that the application knows its virtual
>"location". This may be an empty string, if the application
>corresponds to the "ro
[Graham Dumpleton]
> Should a WSGI adapter for a web server which allows a mount point to
> have a trailing slash specifically flag as a configuration error an
> attempt to use such a mount point given that it appears to be
> incompatible with WSGI?
OK, I'll have a go.
I think the question boils
