[Web-SIG] WSGI & CGI spec

2006-12-17 Thread Ian Bicking
Reading the CGI spec I'm noticing some requirements it makes that aren't done as much in WSGI. In particular: 6.1.8. QUERY_STRING A URL-encoded string; the part of the Script-URI. (See section 3.2.) QUERY_STRING = query-string query-string = *uric The URL syntax for a q

Re: [Web-SIG] WSGI & CGI spec

2006-12-18 Thread Mikeal Rogers
> Lastly it was noted to me that SCRIPT_NAME and PATH_INFO are > supposed to > be decoded (in the spec it says "The syntax and semantics are > similar to > a decoded HTTP URL 'path' token (defined in RFC 2396 [4])"). I > haven't > been doing this, and the spec isn't clear on this (wsgiref do

Re: [Web-SIG] WSGI & CGI spec

2006-12-19 Thread Jason Kirtland
Ian wrote: > Reading the CGI spec I'm noticing some requirements it makes that > aren't done as much in WSGI. > [...] > It's also unclear if the WSGI server is expected to normalize the > path, specifically things like /foo/../bar -- Apache does do > this, wsgiref does not. The spec could definit

Re: [Web-SIG] WSGI & CGI spec

2006-12-19 Thread Phillip J. Eby
At 03:36 PM 12/19/2006 -0800, Jason Kirtland wrote: >To my reading, PEP 333 implies that a server should plop the >Request-URI into PATH_INFO, and it should store it there >unmolested. That's only the case if the address of the application is the root of the server, and then only if the request U

Re: [Web-SIG] WSGI & CGI spec

2006-12-19 Thread Jason Kirtland
Phillip wrote: > At 03:36 PM 12/19/2006 -0800, Jason Kirtland wrote: >> To my reading, PEP 333 implies that a server should plop the >> Request-URI into PATH_INFO, and it should store it there >> unmolested. > > That's only the case if the address of the application is the > root of the server, and

Re: [Web-SIG] WSGI & CGI spec

2006-12-19 Thread Phillip J. Eby
At 04:50 PM 12/19/2006 -0800, Jason Kirtland wrote: >Phillip wrote: > > At 03:36 PM 12/19/2006 -0800, Jason Kirtland wrote: > >> To my reading, PEP 333 implies that a server should plop the > >> Request-URI into PATH_INFO, and it should store it there > >> unmolested. > > > > That's only the case i

Re: [Web-SIG] WSGI & CGI spec

2006-12-20 Thread Jason Kirtland
Phillip wrote: > At 04:50 PM 12/19/2006 -0800, Jason Kirtland wrote: >> What would a server do with an absolute URI vs. abs_path, if not >> place it in PATH_INFO? Or '*', for that matter? > > My understanding is that an absolute URI is equivalent to issuing > the same request with e.g. a 'Host:' h

Re: [Web-SIG] WSGI & CGI spec

2006-12-20 Thread Joe Gregorio
On 12/19/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > My understanding is that an absolute URI is equivalent to issuing the same > request with e.g. a 'Host:' header, and should result in equivalent results > in terms of environment variables. Yes, there should be no difference between the two