URI::InvalidURIError: bad URI(is not URI?):
That’s a strange ID but valid. I even checked the RFC 2396 and {}
is not
a reserved character.
But it is part of the ‘unwise’ set defined by RFC 2396 in:
“2.4.3. Excluded US-ASCII Characters
Although they are disallowed within the URI syntax, we include
here a description of those US-ASCII characters that have been
excluded and the reasons for their exclusion.” http://www.faqs.org/rfcs/rfc2396.html
Just because a URI works in any (or even all) browser(s) doesn’t mean
that it conforms to the standard for URIs.
to be in the ‘unwise’ doesn’t mean
that it not conforms to the standard for URIs.
I’m escaping and it works, but in my option it could be handled by the
lib.
VP
Rob B. wrote:
On Aug 27, 2009, at 10:31 AM, Michael F. wrote:
URI::InvalidURIError: bad URI(is not URI?):
That’s a strange ID but valid. I even checked the RFC 2396 and {}
is not
a reserved character.
But it is part of the ‘unwise’ set defined by RFC 2396 in:
“2.4.3. Excluded US-ASCII Characters
Although they are disallowed within the URI syntax, we include
here a description of those US-ASCII characters that have been
excluded and the reasons for their exclusion.” RFC 2396 - Uniform Resource Identifiers (URI): Generic Syntax (RFC2396)
Just because a URI works in any (or even all) browser(s) doesn’t mean
that it conforms to the standard for URIs.