Gregory (Grisha) Trubetskoy wrote:
> On Wed, 18 May 2005, Robert Brewer wrote:
>
> > I wasn't sure either. The mod_python docs say
> > set_content_length() sets the header for you.
>
> I just happened to be reading this passingly - I don't know
> what the code in question looks like, but IIRC,
On Wed, 18 May 2005, Robert Brewer wrote:
> I wasn't sure either. The mod_python docs say set_content_length() sets
> the header for you.
I just happened to be reading this passingly - I don't know what the code
in question looks like, but IIRC, by setting content-length you disable
chunked en
Phillip J. Eby wrote:
> At 09:40 AM 5/18/2005 -0700, Robert Brewer wrote:
> > After much poring through many specs, I've got a WSGI wrapper for
> > mod_python that I'm fairly comfortable with. I'm sure PJE
> > will find 16 holes in it right away ;)
>
> Nope; not a one that I can see. Although I'
At 09:40 AM 5/18/2005 -0700, Robert Brewer wrote:
>After much poring through many specs, I've got a WSGI wrapper for
>mod_python that I'm fairly comfortable with. I'm sure PJE will find 16
>holes in it right away ;)
Nope; not a one that I can see. Although I'm curious about your choice in
send_h
After much poring through many specs, I've got a WSGI wrapper for
mod_python that I'm fairly comfortable with. I'm sure PJE will find 16
holes in it right away ;) but it fixes some of the problems in the rough
draft I posted here last October.
http://www.amorhq.net/blogs/index.php/fumanchu/2005/05
These references should clear up the confusion; the space is explicitly
required by both PEP 333 and by the HTTP specification:
http://www.python.org/peps/pep-0333.html#the-start-response-callable
http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1
With respect to vagueness in the PEP,
