• From: "David Lee" <dlee@c...>
• To: "'Julian Reschke'" <julian.reschke@g...>
• Date: Mon, 30 Jan 2012 18:43:32 -0500

--- David
A simple insertion of the text "UTF8
 encoded prior to base64" would have nailed it.

------ Julian
If you actually had read the spec, you would know why that doesn't work.

Unless you mean: "back in 1997" (RFC 2068).
---------
Yes I "actually" read the spec but no I dont know why that wouldn't work.
Maybe you could enlighten me ? 
Maybe it's that time travel thing where UTF8 was invented after HTTP ... ?
Is that to which you were referring ?
I've been around for both but honestly can't remember which came first, the
chicken or the egg.


----------------------------------------
David A. Lee
dlee@c...
http://www.xmlsh.org

• Follow-Ups:
  • Re: RE: Encoding charset of HTTP Basic Authentication
    • From: Julian Reschke <julian.reschke@g...>

• References:
  • RE: Encoding charset of HTTP Basic Authentication
    • From: "David Lee" <dlee@c...>
  • Re: RE: Encoding charset of HTTP Basic Authentication
    • From: "Pete Cordell" <petexmldev@c...>
  • Re: RE: Encoding charset of HTTP Basic Authentication
    • From: Petite Abeille <petite.abeille@g...>
  • Re: RE: Encoding charset of HTTP Basic Authentication
    • From: "Pete Cordell" <petexmldev@c...>
  • Re: RE: Encoding charset of HTTP Basic Authentication
    • From: "Pete Cordell" <petexmldev@c...>
  • Re: RE: Encoding charset of HTTP Basic Authentication
    • From: Petite Abeille <petite.abeille@g...>
  • RE: RE: Encoding charset of HTTP Basic Authentication
    • From: "David Lee" <dlee@c...>
  • Re: RE: Encoding charset of HTTP Basic Authentication
    • From: Julian Reschke <julian.reschke@g...>