Re: [hunchentoot-devel] Encoding issues in auhtorization header

Edi Weitz wrote:

My understanding of the standard is that what you are doing is wrong.

I guess, you are right.

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. Regards, Christian