Thanks for pointing it out. I'll correct it. On Oct 22, 10:50 am, dirk <australiandevelo...@gmail.com> wrote: > I've found a bug in the way that the uri is parsed. > If the uri includes an @ in the path, the regular expression causes it > to be included in the authority, so signature generation fails. > For example:http://example.com/userResource/t...@test.com/authenticate > > The regular expression needs a slight modification: > /^(?:([^:\/?#]+):)?(?:\/\/((?:(([^:@]*):?([^:@]*))?@)?([^:\/?#]*)(?:: > (\d*))?))?((((?:[^?#\/]*\/)*)([^?#]*))(?:\?([^#]*))?(?:#(.*))?)/ > /^(?:([^:\/?#]+):)?(?:\/\/((?:(([^:@/]*):?([^:/@]*))?@)?([^:\/?#]*)(?:: > (\d*))?))?((((?:[^?#\/]*\/)*)([^?#]*))(?:\?([^#]*))?(?:#(.*))?)/ > > Basically I added a / to the character class that scans for the @ > symbol, ie [^:@/]
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oauth@googlegroups.com To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
