Manlio Perillo wrote:
In a CGI application, HTTP headers are Unicode strings, and are decoded
using system default encoding.
In a future WSGI application, HTTP headers are Unicode strings, and are
decoded using latin-1 encoding.
Yes. As proposed, WSGI 1.1 would require CGI-to-WSGI handler t
--- On Mon, 12/7/09, Graham Dumpleton wrote:
> For the record, CGI/WSGI adapters should also protect the
> original
> stdin/stdout so WSGI application doesn't cause problems by
> using
> 'print' or do other odd stuff with input. I haven't seen a
> single
> CGI/WSGI adapter which does it in a wa
2009/12/7 Manlio Perillo :
> Graham Dumpleton ha scritto:
>
> Note: I'm sending the entire message to the mailing list.
>
>> 2009/12/7 Manlio Perillo :
>>> Hi.
>>>
>>> I'm playing with Python 3.x, current revision.
>>>
>>> I have noted that the data in the os.environ are noe Unicode strings.
>>>
>>
Graham Dumpleton ha scritto:
Note: I'm sending the entire message to the mailing list.
> 2009/12/7 Manlio Perillo :
>> Hi.
>>
>> I'm playing with Python 3.x, current revision.
>>
>> I have noted that the data in the os.environ are noe Unicode strings.
>>
>> In a CGI application, HTTP headers are
Hi.
I'm playing with Python 3.x, current revision.
I have noted that the data in the os.environ are noe Unicode strings.
In a CGI application, HTTP headers are Unicode strings, and are decoded
using system default encoding.
In a future WSGI application, HTTP headers are Unicode strings, and are
