[Web-SIG] Relationship between SCRIPT_NAME and PATH_INFO.

[Phillip J. Eby]

At 07:07 PM 1/28/2007 +0000, 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 with WSGI?
>
>[snip]
>I don't know if this provides any insight into whether or not mounting
>applications with a trailing slash is an error.
>
>Does that help at all?

I think it's safe to say that WSGI does not permit an application to live 
at a mount point with a trailing '/', unless it is the root of the host.

Whether this is a good thing or not is a separate question.  In truth, it 
had never occurred to me that such a thing was possible or practical.  If 
you look at the wsgiref.util.shift_path_info(), you'll see that it supports 
the possibility of having a trailing slash on a URL, and treating it 
differently, but the assumption is that all WSGI applications live at 
either the root or a location without a trailing /.

Given the weird effects that result from trying to manage relative names 
and other such complications of the idea, I don't think we should extend 
WSGI to allow applications to live at non-root URLs with trailing 
slashes.  They should live at the named location, and optionally get a 
PATH_INFO.  It's up to the application to interpret the trailing /, if any.