<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On further inspection, the instructions as written in 2.1.1/2.1.2
don't actually allow for the acct: URI scheme. The acct: scheme is a
non-heirarchical URI, which means it doesn't include the "//"
component, and the text currently states:<br>
<br>
<blockquote>a URI either in the form of <tt>scheme "://" authority
path-abempty [ "?" query ] [ "#" fragment ]</tt> or <tt>authority
path-abempty [ "?" query ] [ "#" fragment ]</tt> per <a
class="info"
href="http://openid.net/specs/openid-connect-discovery-1_0.html#RFC3986">RFC
3986</a> [RFC3986]. <br>
</blockquote>
<br>
I think this needs an errata published as the intent was more like:<br>
<br>
<br>
<blockquote>a URI in the form of <tt>scheme "://" authority
path-abempty [ "?" query ] [ "#" fragment ]</tt>, <tt>authority
path-abempty [ "?" query ] [ "#" fragment ],</tt>
<b> or scheme ":" userinfo "@" host</b> per <a class="info"
href="http://openid.net/specs/openid-connect-discovery-1_0.html#RFC3986">RFC
3986</a> [RFC3986]. <br>
</blockquote>
<br>
I'll add an issue with this text shortly.<br>
<br>
-- Justin<br>
<br>
<div class="moz-cite-prefix">On 06/27/2013 02:21 PM, Justin Richer
wrote:<br>
</div>
<blockquote cite="mid:MLQM-20130627151435370-4223@mlite.mitre.org"
type="cite">I've been working on the webfinger handler for our
client software, and I am having a terrible time trying to get the
actual parsing rules straight and provide consistent output with
the example input values. Specifically, when using the Regex in
Appendix B of RFC3986 (and several derivatives such as that used
by Spring's UriComponentsBuilder), the "path" component seems to
eat things that it shouldn't. For instance, with the input
<a class="moz-txt-link-rfc2396E" href="mailto:joe@example.com">"joe@example.com"</a>, I get the entire string put into the "path"
component and everything else null. Similar thing happens with the
<a class="moz-txt-link-rfc2396E" href="mailto:acct:juliet%40capulet.example@shoppingsite.example.com">"acct:juliet%40capulet.example@shoppingsite.example.com"</a> example,
with the "acct" being parsed as the scheme and everything else
getting dumped into the path.
<br>
<br>
How is everyone else parsing user input? Are you able to follow
all of the input parsing and normalization rules described in the
discovery document? And if you're working in Java, can you point
me at your code or the library that you're using to do it? (Note
that Java's built-in URI parser falls over for other reasons.)
<br>
<br>
-- Justin
<br>
_______________________________________________
<br>
Openid-specs-ab mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
<br>
<br>
</blockquote>
<br>
</body>
</html>