STOP SENDING ME THIS SPAM.TAKE ME OUT OF UR GROUP,WILL MUCH APPRECIATE UR COOPERATION!<br><br>
<div><span class="gmail_quote">On 4/23/06, <b class="gmail_sendername">Samar Sodhi</b> <<a href="mailto:samarsodhi@gmail.com">samarsodhi@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div style="DIRECTION: ltr">STO SENDING ME THIS SPAM.TAKE ME OUT OF UR GROUP,WILL MUCH APPRECIATE UR COOPERATION!</div>
<div style="DIRECTION: ltr"><span class="e" id="q_10ac42c23dd21895_1"><br><br>
<div><span class="gmail_quote">On 4/22/06, <b class="gmail_sendername">Thomas Broyer</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:t.broyer@gmail.com" target="_blank">t.broyer@gmail.com</a>
> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">2006/4/21, Johannes Ernst <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:jernst+lists.danga.com@netmesh.us" target="_blank">
jernst+lists.danga.com@netmesh.us </a>>:<br>> Well, speaking just about our code at NetMesh, we currently would<br>> have two entries in our Yadis cache for URLs<br>> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://foo.com/a%20b" target="_blank">
http://foo.com/a%20b</a><br>> and<br>> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://foo.com/a+b" target="_blank">http://foo.com/a+b</a><br>> and chances are that if you brought those two URLs to the same
<br>> Relying Party based on our code, they would create separate<br>> "accounts" in the database. I consider that a bug ... because there <br>> is no practical way that<br>> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://foo.com/a%20b" target="_blank">
http://foo.com/a%20b</a><br>> and<br>> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://foo.com/a+b" target="_blank">http://foo.com/a+b</a><br>> could produce different web pages when entered into a browser.
<br><br>I consider that a bug, because "+" is not equivalent to a space per RFC3986 [1].<br><br>Correct me if I'm wrong, but they're only equivalent in the query part<br>of a URI when following application/x-www-form-urlencoded [2] style,
<br>such as HTML forms using GET method, never in the path part of the<br>URI, where a "+" is always left as-is [*] or encoded as "%2B".<br><br>[*] because the "+" sign has no delimiting role in the "http" or
<br>"https" schemes ; per RFC3986, section 2.2, §4 (which says that "If a<br>reserved character is found in a URI component and no delimiting role<br>is known for that character, then it must be interpreted as
<br>representing the data octet corresponding to that character's encoding<br>in US-ASCII.") and RFC2616 (which assigns no delimiting role to "+")<br><br>[1] <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.gbiv.com/protocols/uri/rfc/rfc3986.html" target="_blank">
http://www.gbiv.com/protocols/uri/rfc/rfc3986.html</a><br>[2] <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.w3.org/TR/html4/interact/forms.html#h-17.13.4.1" target="_blank">http://www.w3.org/TR/html4/interact/forms.html#h-17.13.4.1
</a><br><br>--<br>Thomas Broyer<br></blockquote></div><br><br clear="all"><br></span></div>
<div style="DIRECTION: ltr">-- <br> </div>
<div style="DIRECTION: ltr"><span class="sg">Samar </span></div></blockquote></div><br><br clear="all"><br>-- <br>Samar