Re: [Web-SIG] HEAD requests, WSGI gateways, and middleware

2008-01-27 Thread Graham Dumpleton
On 25/01/2008, Brian Smith <[EMAIL PROTECTED]> wrote: > My application correctly responds to HEAD requests as-is. However, it doesn't > work with middleware that sets headers based on the content of the response > body. > > For example, a gateway or middleware that sets ETag based on an checksum,

Re: [Web-SIG] environ["wsgi.input"].read()

2008-01-27 Thread Graham Dumpleton
On 28/01/2008, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On 28/01/2008, Brian Smith <[EMAIL PROTECTED]> wrote: > > Graham Dumpleton wrote: > > > On 26/01/2008, Brian Smith <[EMAIL PROTECTED]> wrote: > > > As to your questions about read() with no argument, or with > > > traditional Python file

Re: [Web-SIG] environ["wsgi.input"].read()

2008-01-27 Thread Graham Dumpleton
On 28/01/2008, Brian Smith <[EMAIL PROTECTED]> wrote: > Manlio Perillo wrote: > > Graham Dumpleton ha scritto: > > > On 27/01/2008, Manlio Perillo <[EMAIL PROTECTED]> wrote: > > >> This is just a suggestion, but what about "requiring" that a WSGI > > >> implementation calls the WSGI application onl

Re: [Web-SIG] environ["wsgi.input"].read()

2008-01-27 Thread Brian Smith
Manlio Perillo wrote: > Graham Dumpleton ha scritto: > > On 27/01/2008, Manlio Perillo <[EMAIL PROTECTED]> wrote: > >> This is just a suggestion, but what about "requiring" that a WSGI > >> implementation calls the WSGI application only when all > >> the request body has been read? > > > > Can't

Re: [Web-SIG] environ["wsgi.input"].read()

2008-01-27 Thread Manlio Perillo
Graham Dumpleton ha scritto: > On 27/01/2008, Manlio Perillo <[EMAIL PROTECTED]> wrote: >> Graham Dumpleton ha scritto: >>> [...] >> > >>> I have brought up the issue of chunked encoding and mutating input >>> filters previously, whether they be implemented in Apache or as WSGI >>> middleware. For

Re: [Web-SIG] environ["wsgi.input"].read()

2008-01-27 Thread Graham Dumpleton
On 27/01/2008, Manlio Perillo <[EMAIL PROTECTED]> wrote: > Graham Dumpleton ha scritto: > > [...] > > > > > > I have brought up the issue of chunked encoding and mutating input > > filters previously, whether they be implemented in Apache or as WSGI > > middleware. For the outcome of that discussi

Re: [Web-SIG] environ["wsgi.input"].read()

2008-01-27 Thread Graham Dumpleton
On 28/01/2008, Brian Smith <[EMAIL PROTECTED]> wrote: > Graham Dumpleton wrote: > > On 26/01/2008, Brian Smith <[EMAIL PROTECTED]> wrote: > > As to your questions about read() with no argument, or with > > traditional Python file like object default of -1, the only > > WSGI server/adapter I know of

Re: [Web-SIG] environ["wsgi.input"].read()

2008-01-27 Thread Brian Smith
Graham Dumpleton wrote: > On 26/01/2008, Brian Smith <[EMAIL PROTECTED]> wrote: > As to your questions about read() with no argument, or with > traditional Python file like object default of -1, the only > WSGI server/adapter I know of where this will NOT work as one > would expect, ie., read re

Re: [Web-SIG] URL quoting in WSGI (or the lack therof)

2008-01-27 Thread Luis Bruno
Hello, it's me again, Phillip J. Eby wrote: > MoinMoin, for example, has its own encoding scheme for handling > pseudo-slashes in paths, and IMO it's a better way to handle it than > trying to rely on finding a server that supports *not* decoding URLs. I had the abstract knowledge that CGI is

Re: [Web-SIG] environ["wsgi.input"].read()

2008-01-27 Thread Manlio Perillo
Graham Dumpleton ha scritto: > [...] > > > I have brought up the issue of chunked encoding and mutating input > filters previously, whether they be implemented in Apache or as WSGI > middleware. For the outcome of that discussion see: > > > http://groups.google.com/group/python-web-sig/browse