[OpenID] UTF-8 processing
John Panzer
jpanzer at aol.net
Sat Apr 14 17:04:55 UTC 2007
Tan, William wrote:
>Josh Hoyt wrote:
>
>
>>On 4/11/07, Tan, William <William.Tan at neustar.biz> wrote:
>>
>>
>>>"The keys and values permit the full Unicode character set (UCS). When
>>>the keys and values need to be converted to/from bytes, they MUST first
>>>be represented in the UTF-8 [RFC3629] and then percent encoded
>>>[RFC3986]."
>>>
>>>
>>Percent encoding only happens when the message is sent as
>>x-www-urlencoded or as query parameters. When using key-value encoding
>>from the OpenID specification (e.g. association responses), nothing is
>>percent-encoded.
>>
>>Josh
>>
>>
>You're right. Should the content-type returned in association responses
>be tagged as such? I.e. "text/plain; charset=UTF-8"
>
>
+1 if at all possible. Is it possible that some implementations may not
have full control over the Content-Type: header however?
--
Abstractioneer <http://feeds.feedburner.com/aol/SzHO>John Panzer
System Architect
http://abstractioneer.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20070414/bf692ddd/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SzHO.gif
Type: image/gif
Size: 9130 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20070414/bf692ddd/attachment-0002.gif>
More information about the general
mailing list