Phillip J. Eby ha scritto:
> At 06:21 PM 10/15/2007 +0200, Manlio Perillo wrote:
>> Phillip J. Eby ha scritto:
>> > At 05:52 PM 10/15/2007 +0200, Manlio Perillo wrote:
>> >> Hi.
>> >>
>> >> I'm implementing the start_response callable for Nginx mod_wsgi and I
>> >> have a few questions.
>> >>
>> >>
At 06:21 PM 10/15/2007 +0200, Manlio Perillo wrote:
>Phillip J. Eby ha scritto:
> > At 05:52 PM 10/15/2007 +0200, Manlio Perillo wrote:
> >> Hi.
> >>
> >> I'm implementing the start_response callable for Nginx mod_wsgi and I
> >> have a few questions.
> >>
> >> 1) From the WSGI PEP it seems that an
Phillip J. Eby ha scritto:
> At 05:52 PM 10/15/2007 +0200, Manlio Perillo wrote:
>> Hi.
>>
>> I'm implementing the start_response callable for Nginx mod_wsgi and I
>> have a few questions.
>>
>> 1) From the WSGI PEP it seems that an implementation is allowed to
>> *always* raise an exception wh
At 05:52 PM 10/15/2007 +0200, Manlio Perillo wrote:
>Hi.
>
>I'm implementing the start_response callable for Nginx mod_wsgi and I
>have a few questions.
>
>1) From the WSGI PEP it seems that an implementation is allowed to
> *always* raise an exception when start_response is called with a not
>
Manlio Perillo ha scritto:
> Hi.
>
> I'm implementing the start_response callable for Nginx mod_wsgi and I
> have a few questions.
>
> [...]
>
> 2) What happens if an application call start_response with an incorrect
> status line or headers?
>
> Should an implementation consider the f
Hi.
I'm implementing the start_response callable for Nginx mod_wsgi and I
have a few questions.
1) From the WSGI PEP it seems that an implementation is allowed to
*always* raise an exception when start_response is called with a not
null exc_info.
Is this true?
2) What happens if an
