Project

General

Profile

Bug #2525

URI#normalize incomplete

Added by marcandre (Marc-Andre Lafortune) over 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Target version:
ruby -v:
ruby 1.9.2dev (2009-12-24 trunk 26163) [x86_64-darwin10.2.0]
[ruby-core:27309]

Description

=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

History

#1 Updated by naruse (Yui NARUSE) over 7 years ago

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

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

#2 Updated by vvs (Vladimir Sizikov) over 7 years ago

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

#3 Updated by naruse (Yui NARUSE) over 7 years ago

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

#4 Updated by marcandre (Marc-Andre Lafortune) over 7 years ago

  • 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

#5 Updated by naruse (Yui NARUSE) over 7 years ago

  • 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

Also available in: Atom PDF