On Thu, Dec 03, 2009 at 08:33:19PM +0100, Manlio Perillo wrote:
> Right now I'm doing a: username.decode('us-ascii', 'replace')
Or like most frameworks you could let the application author deal with
the problem, just pass the raw strings to the application.
--
Henry Prêcheur
__
Henry Precheur ha scritto:
> [...]
>> How is authorization username handled in common WSGI frameworks?
>
> As far as I know, they don't handle this. They just return the string
> without dealing with the encoding issues.
>
> I think there is no correct way of handling this, because 99% of
> usern
On Thu, Dec 03, 2009 at 05:09:31PM +0100, Manlio Perillo wrote:
> This is really a mess.
RFC 2617 doesn't specify any encoding for its headers, so it should be
latin-1 everywhere. But on the web nobody respect standards.
> How is authorization username handled in common WSGI frameworks?
As far a
Manlio Perillo wrote:
I have written a simple WSGI application that asks authentication
credentials
Ho ho! This is another area that is Completely Broken Everywhere. It's
actually a similar situation to the cookies:
- Opera and Chrome send non-ASCII cookie characters in UTF-8.
- IE encodes
Manlio Perillo ha scritto:
> Hi.
>
> I'm doing some tests to try to understand how HTTP headers are encoded
> by browsers.
>
> I have written a simple WSGI application that asks authentication
> credentials and then print them on the terminal and return the data as
> response, as raw bytes
> http
Hi.
I'm doing some tests to try to understand how HTTP headers are encoded
by browsers.
I have written a simple WSGI application that asks authentication
credentials and then print them on the terminal and return the data as
response, as raw bytes
http://paste.pocoo.org/show/154633/
Then I used
