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:' header,
On 12/20/06, Phillip J. Eby [EMAIL PROTECTED] wrote:
At 12:06 PM 12/20/2006 -0800, Guido van Rossum wrote:
On 12/20/06, Phillip J. Eby [EMAIL PROTECTED] wrote:
At 10:12 AM 12/20/2006 -0800, Guido van Rossum wrote:
We're struggling to use wsgiref behind some Googlish infrastructure,
and one
Sylvain Hellegouarch wrote:
Well, we're using wsgiref's simple_server which only speaks HTTP/1.0,
but we really need to speak HTTP/1.1 and use chunked. Where do you
recommend we put the chunking instead?
shameless-plug
If you are not to fuss about which WSGI server you can afford to use,
Guido,
Well, we're using wsgiref's simple_server which only speaks HTTP/1.0,
but we really need to speak HTTP/1.1 and use chunked. Where do you
recommend we put the chunking instead?
shameless-plug
If you are not to fuss about which WSGI server you can afford to use,
you could grab the
At 08:51 PM 12/20/2006 +, Sylvain Hellegouarch wrote:
[1] http://www.cherrypy.org/browser/trunk/cherrypy/wsgiserver.py
Guido, it does appear that this server implements chunked encoding if you:
1. Use a status of 200, 203, or 206
2. Don't include a Content-Length header
3. *Yield* each
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
