• From: Richard Salz <rsalz@u...>
• To: "David Lee" <dlee@c...>
• Date: Wed, 1 Feb 2012 11:23:06 -0500

My wording wasn't clear enough.

At the time, we all thought "netascii for headers" was the right thing to 
do.  So much so that the question of codesets in headers *never came up.* 
The entire IETF had this mindset, it was a truism, fundamental concept, 
statement of fact, fundamental postulate, etc. It was not "what about 
charset encodings?  Never mind"

I use the pronoun "we" on purpose; 
http://www.w3.org/Protocols/rfc2616/rfc2616-sec16.html#sec16

        /r$

--
STSM, WebSphere Appliance Architect
https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/

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

• References:
  • Re: RE: Encoding charset of HTTP Basic Authentication
    • From: Michael Kay <mike@s...>
  • RE: RE: Encoding charset of HTTP Basic Authentication
    • From: "David Lee" <dlee@c...>
  • Re: RE: Encoding charset of HTTP Basic Authentication
    • From: Tei <oscar.vives@g...>
  • Re: RE: Encoding charset of HTTP Basic Authentication
    • From: Richard Salz <rsalz@u...>
  • RE: RE: Encoding charset of HTTP Basic Authentication
    • From: "David Lee" <dlee@c...>