On 2011-10-05 01:56, William Mills wrote:
Allowing URI requires allowing % encoding, which is workable. As far as
the protocol goes URI is a form of space separated string and the
protocol doesn't care. URI doesn't include quote or qhitespace in the
allowed characters so there's no problem there.
I agree that we'd have to write it such that it's clear you don't have
to use a URI. Drawing from
http://labs.apache.org/webarch/uri/rev-2002/rfc2396bis.html#path perhaps
the allowed charset becomes
...
Note that RFC 2396 has been obsoleted by RFC 3986 a long time ago. Don't
use it as base syntax.
Best regards, Julian
_______________________________________________
OAuth mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/oauth
