[Openid-specs-ab] User input normalization and parsing

John Bradley ve7jtb at ve7jtb.com
Sun Jun 30 17:19:15 UTC 2013


Per my other email to the list Java is doing the correct thing there is no authority segment for acct: it is all path.  

If it were acct://boo@foo.com then it would parse as a higher-part and find the host and user.   That is a acct URI issue.

John B.
On 2013-06-27, at 2:21 PM, Justin Richer <jricher at mitre.org> wrote:

> 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 "joe at example.com", I get the entire string put into the "path" component and everything else null. Similar thing happens with the "acct:juliet%40capulet.example at shoppingsite.example.com" example, with the "acct" being parsed as the scheme and everything else getting dumped into the path.
> 
> 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.)
> 
> -- Justin
> 
> -- 
> You received this message because you are subscribed to the Google Groups "OpenID Connect Interop" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to openid-connect-interop+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4507 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20130630/38f55212/attachment.p7s>


More information about the Openid-specs-ab mailing list