<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Tan, William wrote:
<blockquote cite="mid461D58E9.7020401@neustar.biz" type="cite">
<pre wrap="">Josh Hoyt wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 4/11/07, Tan, William <a class="moz-txt-link-rfc2396E" href="mailto:William.Tan@neustar.biz"><William.Tan@neustar.biz></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">"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]."
</pre>
</blockquote>
<pre wrap="">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
</pre>
</blockquote>
<pre wrap=""><!---->You're right. Should the content-type returned in association responses
be tagged as such? I.e. "text/plain; charset=UTF-8"
</pre>
</blockquote>
+1 if at all possible. Is it possible that some implementations may
not have full control over the Content-Type: header however?<br>
<br>
<div class="moz-signature">-- <br>
<br>
<a href="http://feeds.feedburner.com/aol/SzHO"><img
src="cid:part1.03000206.04050203@aol.net"
style="border: 0pt none ; float: right;" alt="Abstractioneer"></a>John
Panzer<br>
System Architect<br>
<a class="moz-txt-link-freetext" href="http://abstractioneer.org">http://abstractioneer.org</a><br>
</div>
</body>
</html>