That's my point. The spec says " Words of *TEXT MAY contain characters from character sets other than ISO- 8859-1 [22] only when encoded according to the rules of RFC 2047 [14]." But since RFC 2047 is a dead letter as a practical matter the only safe way to move non-ASCII content in a HTTP header is to use some form of ASCII encoding. So, for example, we couldn't use UTF-16 because it produces characters that aren't safe in ASCII.
> -----Original Message----- > From: Robert Sayre [mailto:[email protected]] > Sent: Tuesday, July 13, 2010 4:01 PM > To: Yaron Goland > Cc: Eran Hammer-Lahav; OAuth WG > Subject: Re: [OAUTH-WG] What to do about 'realm' > > On Tue, Jul 13, 2010 at 9:46 AM, Yaron Goland <[email protected]> > wrote: > > As defined in section 4.2 of RFC 2616 the only characters legally allowed > > in a > HTTP header are a fairly small subset of ASCII. > > I don't think that is correct. The definition of the TEXT rule in section 2.2 > allows most octets. It also references RFC 2047, but I don't think many > implementations actually support that RFC. > > > -- > > Robert Sayre > > "I would have written a shorter letter, but I did not have the time." _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
