If you specify it. It is supported but not required. EHL
On Jul 16, 2010, at 16:16, "Brian Eaton" <bea...@google.com> wrote: > On Fri, Jul 16, 2010 at 11:21 AM, Yaron Goland <yar...@microsoft.com> wrote: >> 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. > > Of course, JSON does support unicode escapes, which will work just > fine in an HTTP header. > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
