The way you've interpreted it, Allen, is the way .NET interprets it, I know that. I'm not sure about whether that's part of the URI spec or not. I was just thinking that in some of the less robust OpenID libraries that might have a string search and a for loop going through looking for each key=value that is supposed to be present that they'd miss the additional ones.<div>
<br clear="all">--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - Voltaire<br>
<br><br><div class="gmail_quote">On Wed, Mar 11, 2009 at 1:57 PM, Allen Tom <span dir="ltr"><<a href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm a little rusty on query parameter syntax, but isn't<br>
<br>
key=value1&key=value2&key=value3<br>
<br>
equivalent to<br>
<br>
key=value1,value2,value3<br>
<br>
Should the spec address this case?<br><font color="#888888">
<br>
Allen</font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
Breno de Medeiros wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
What if they appear a fewer number of times?<br>
<br>
The correct language is that the set of parameter assignments "a=b", where 'a' is the key and 'b' is the value, that appear in the HTTP request the RP received, and that are not OpenID parameters, should be identical to the set of assignments present in the query part of the return_to URL in the authentication response.<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div>