Project

General

Profile

Bug #8352

Updated by knu (Akinori MUSHA) over 2 years ago

RFC 2396 2896 (on which the library currently is based) or RFC 3986 says nothing about a sequence of slashes in the path part except for parsing rules when a URI (path) starts with two slashes. 

 It should be perfectly valid to have a slash right after another, and there is no reason to "normalize" a sequence of slashes into a single slash, which uri actually does in merging paths: 

 ~~~ 
 URI.parse('http://example.com/foo//bar/')+'.' 
 => #<URI::HTTP:0x0000080303d2b0 URL:http://example.com/foo/bar/> 
 ~~~ 

 Fixing this may be as easy as changing the regexp in URI::Generic#split_path from %r{/+} to %r{/}, but I wonder how the impact of incompatibility it may introduce would be.

Back