<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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">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">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">general-request@openid.net</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-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; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">Message: 1<br>Date: Thu, 8 Jan 2009 00:58:45 -0800<br>From: "Chris Messina" <<a href="mailto:chris.messina@gmail.com">chris.messina@gmail.com</a>><br>Subject: [OpenID] HTML-Based Discovery incompatibilities<br>To: "<a href="mailto:general@openid.net">general@openid.net</a><span class="Apple-converted-space"> </span>List" <<a href="mailto:general@openid.net">general@openid.net</a>><br>Message-ID:<br><span class="Apple-tab-span" style="white-space: pre; "> </span><<a href="mailto:1bc4603e0901080058u2ae8f88dw87f268460e1605c8@mail.gmail.com">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/">http://factoryjoe.com/blog/</a>" /><br> <link rel="openid2.local_id openid.delegate" href="<br><a href="http://factoryjoe.com/blog/">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">http://factoryjoe.com/blog/?openid_server=1</a>" /><br> <link rel="openid2.local_id" href="<br><a href="http://factoryjoe.com/blog/author/factoryjoe/">http://factoryjoe.com/blog/author/factoryjoe/</a>" /><br> <link rel="openid.server" href="<br><a href="http://factoryjoe.com/blog/?openid_server=1">http://factoryjoe.com/blog/?openid_server=1</a>" /><br> <link rel="openid.delegate" href="<br><a href="http://factoryjoe.com/blog/author/factoryjoe/">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></body></html>