[hunchentoot-devel] Encoding issues in auhtorization header

[Edi Weitz]

On Wed, 14 May 2008 21:10:26 +0200, Christian Haselbach <ch at mr-co.de> wrote:

>> So, you'd have to add support for proper RFC 2047 parsing to make
>> the function deal with this correctly.  (And I'd say that that
>> would probably be worth its own library, maybe based on
>> FLEXI-STREAMS.)
>>   
> Well, yes, looks like it. It seems to be a bit overprotective to
> have something base64 encoded and then again encoded inside, which
> might again use base64.

And, BTW, it probably won't buy you much unless the main browsers play
along.  I just tried with Firefox 2.0 and if you enter characters as
login or password which aren't in Latin-1, Firefox simply sends the
lower octet of each character's code point.  Not very helpful...