Bug #2525: URI#normalize incomplete

• Status: Closed
• Assignee: akira (akira yamada)
• Target version: 1.9.2
• ruby -v: ruby 1.9.2dev (2009-12-24 trunk 26163) [x86_64-darwin10.2.0]

[marcandre (Marc-Andre Lafortune)]

=begin
"hTTp://example.com/" and "http://exa%4dple.com/" should both be normalized to "http://example.com/" as per RFC 3986.

They currently are not and thus not considered ==.

Tests added to RubySpec
=end

[naruse (Yui NARUSE)]

• Category set to lib
• Status changed from Assigned to Rejected

=begin
URI#normalize is based on RFC 2396.
=end

[vvs (Vladimir Sizikov)]

=begin
If this ticket is rejected, should the RubySpecs reverted as well? Otherwise, they'll continue to fail on all implementations.
=end

[naruse (Yui NARUSE)]

=begin
Yes.
Current URI is based on RFC 2396, so this needs success.
=end

[marcandre (Marc-Andre Lafortune)]

• Status changed from Rejected to Assigned
• Target version set to 1.9.2

=begin
I'll break this issue in two, then.

"hTTp://example.com/" should be normalized to "http://example.com/" as per RFC 2396

http://tools.ietf.org/html/rfc2396#section-3.1 (2nd paragraph)

Scheme names consist of a sequence of characters beginning with a
lower case letter and followed by any combination of lower case
letters, digits, plus ("+"), period ("."), or hyphen ("-").  For
resiliency, programs interpreting URI should treat upper case letters
as equivalent to lower case in scheme names (e.g., allow "HTTP" as
well as "http").

=end

[naruse (Yui NARUSE)]

• Status changed from Assigned to Closed
• % Done changed from 0 to 100

=begin
This issue was solved with changeset r26227.
Marc-Andre, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

=end