On Jan 29, 2008, at 1:36 AM, Brian Smith wrote:
> 1. The WSGI gateway must send the response headers immediately when
> the application yields its first non-empty string.
>
> 2. When there is an "100-continue" token in the request "Expect:"
> header, the WSGI gateway is allowed to delay sendi
1. The WSGI gateway must send the response headers immediately when the
application yields its first non-empty string.
2. When there is an "100-continue" token in the request "Expect:" header, the
WSGI gateway is allowed to delay sending the "100 Continue" response until the
application reads f
Manlio Perillo wrote:
> Ian Bicking ha scritto:
> >
>> [...]
>>
>>> 1) Do not change SCRIPT_NAME, and instead add a wsgiorg.consumed_path, a
>>> list.
>>>
>>> This means that the request uri recostruction must be changed:
>>> SCRIPT_NAME = SCRIPT_NAME + '/'.join(wsgiorg.consumed_path)
Andrew Clover wrote:
> Manlio Perillo wrote:
> > what about "requiring" that a WSGI implementation calls the WSGI
> > application only when all the request body has been read?
>
> Regardless of the discussed technical issues, 'no thanks' -
> this would make it impossible to write - to choose an
Manlio Perillo wrote:
> what about "requiring" that a WSGI implementation calls the WSGI application
> only when all the request body has been read?
Regardless of the discussed technical issues, 'no thanks' - this would
make it impossible to write - to choose an example from production code
- a
Ian Bicking ha scritto:
>
> [...]
>
>> 1) Do not change SCRIPT_NAME, and instead add a wsgiorg.consumed_path, a
>> list.
>>
>> This means that the request uri recostruction must be changed:
>> SCRIPT_NAME = SCRIPT_NAME + '/'.join(wsgiorg.consumed_path)
>
> I suppose you could leave st
