Re: [Web-SIG] Relationship between SCRIPT_NAME and PATH_INFO.

2007-01-28 Thread Phillip J. Eby
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

Re: [Web-SIG] Relationship between SCRIPT_NAME and PATH_INFO.

2007-01-28 Thread Ian Bicking
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

Re: [Web-SIG] Relationship between SCRIPT_NAME and PATH_INFO.

2007-01-28 Thread Alan Kennedy
[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

[Web-SIG] Relationship between SCRIPT_NAME and PATH_INFO.

2007-01-26 Thread Graham Dumpleton
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 "root" of the server. PATH_INFO The r