Thanks John.<div><br></div><div>Yeah, rel-me is from microformats and should be legit. I had that initially as well but found that too many RPs failed on me, so I removed it.</div><div><br></div><div>This should definitely be fixed if it's a problem with the core libs.</div>
<div><br></div><div>Chris<br><br><div class="gmail_quote">On Thu, Jan 8, 2009 at 11:08 AM, John Bradley <span dir="ltr"><<a href="mailto:john.bradley@wingaa.com">john.bradley@wingaa.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">Hi Chris,<div><br></div><div>Yes it is a problem I have detected with a number of RP libs. </div><div><br></div><div>I did a test for openID delegation via rel links for the last OSIS interop</div>
<div><a href="http://osis.idcommons.net/wiki/I5:FeatureTest-OpenID_2.0_Relying_Party_openID_2.0_delegations_via_rel_links" target="_blank">http://osis.idcommons.net/wiki/I5:FeatureTest-OpenID_2.0_Relying_Party_openID_2.0_delegations_via_rel_links</a></div>
<div><br></div><div>One of the leading causes of delegation failure I have seen is using <link rel="me openid.delegate" href="<a href="http://thread-safe.net" target="_blank">http://thread-safe.net</a>" /></div>
<div><br></div><div>A number of the libs I discovered were trying to use regex to find the openid.delegate in a too restrictive way.</div><div><br></div><div>I will expand the test cases for I5 and try to catch this behavior.</div>
<div><br></div><div>Regards</div><div>=jbradley</div><div><br><div><div>On 8-Jan-09, at 1:21 PM, <a href="mailto:general-request@openid.net" target="_blank">general-request@openid.net</a> wrote:</div><br><blockquote type="cite">
<span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Message: 1<br>
Date: Thu, 8 Jan 2009 00:58:45 -0800<br>From: "Chris Messina" <<a href="mailto:chris.messina@gmail.com" target="_blank">chris.messina@gmail.com</a>><br>Subject: [OpenID] HTML-Based Discovery incompatibilities<br>
To: "<a href="mailto:general@openid.net" target="_blank">general@openid.net</a><span> </span>List" <<a href="mailto:general@openid.net" target="_blank">general@openid.net</a>><br>Message-ID:<br><span style="white-space:pre"> </span><<a href="mailto:1bc4603e0901080058u2ae8f88dw87f268460e1605c8@mail.gmail.com" target="_blank">1bc4603e0901080058u2ae8f88dw87f268460e1605c8@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br><br>I just read over SS 7.3.3 on HTML-Based Discovery [1], and considering my<br>experience today trying to re-delegate my OpenID, I've discovered that this<br>
section needs to updated a clarified.<br><br>It turns out that relying parties are not parsing HTML rel values in a<br>standard way. That is, if there is more than one rel value provided for a<br>link, some RPs fail, whereas others work fine.<br>
<br>In other words, this:<br><br> <link rel="openid2.provider openid.server" href="<br><a href="http://factoryjoe.com/blog/" target="_blank">http://factoryjoe.com/blog/</a>" /><br> <link rel="openid2.local_id openid.delegate" href="<br>
<a href="http://factoryjoe.com/blog/" target="_blank">http://factoryjoe.com/blog/</a>" /><br><br>is not the same as this:<br><br> <link rel="openid2.provider" href="<br><a href="http://factoryjoe.com/blog/?openid_server=1" target="_blank">http://factoryjoe.com/blog/?openid_server=1</a>" /><br>
<link rel="openid2.local_id" href="<br><a href="http://factoryjoe.com/blog/author/factoryjoe/" target="_blank">http://factoryjoe.com/blog/author/factoryjoe/</a>" /><br> <link rel="openid.server" href="<br>
<a href="http://factoryjoe.com/blog/?openid_server=1" target="_blank">http://factoryjoe.com/blog/?openid_server=1</a>" /><br> <link rel="openid.delegate" href="<br><a href="http://factoryjoe.com/blog/author/factoryjoe/" target="_blank">http://factoryjoe.com/blog/author/factoryjoe/</a>" /><br>
<br>It's my understanding that the rel attribute should be able to contain<br>several values.<br>But I can tell you that IntenseDebate, for example, failed when delegation<br>was setup using the former code. It only worked when I broke out the two<br>
links into four.<br><br>I'm not sure if this is an issue with the libraries or what, but I'd like to<br>know if other people have experienced this problem, and if we can improve<br>the language in the spec to make sure that people understand that they need<br>
to look for the presence of an element in a rel value -- not that the<br>*entire* value is one element.<br><br>Chris<br></span></blockquote></div><br></div></div></blockquote></div><br><br clear="all"><br>-- <br>Chris Messina<br>
Citizen-Participant &<br> Open Web Advocate-at-Large<br><br><a href="http://factoryjoe.com">factoryjoe.com</a> # <a href="http://diso-project.org">diso-project.org</a><br><a href="http://citizenagency.com">citizenagency.com</a> # <a href="http://vidoop.com">vidoop.com</a><br>
This email is: [ ] bloggable [X] ask first [ ] private<br>
</div>