[Chicken-janitors] #396: Handle empty path components in uri-generic/uri-common

[Chicken Trac]

#396: Handle empty path components in uri-generic/uri-common
------------------------------------------------------+---------------------
 Reporter:  sjamaan                                   |       Owner:  sjamaan
     Type:  defect                                    |      Status:  new    
 Priority:  minor                                     |   Milestone:  4.7.0  
Component:  extensions                                |     Version:  4.6.x  
 Keywords:  uri, pedantic strictness, rfc, standards  |  
------------------------------------------------------+---------------------
 A quick check of the spec seems to indicate that "http://foo.com/bar//qux";
 is a valid URI and should be parsed into {{{#(URI scheme=http
 authority=#(URIAuth host="foo.com" port=#f) path=(/ "bar" "" "qux")
 query=#f fragment=#f)}}} (ie with an empty string in between foo and bar
 in the record's "path" slot)

 Do some more investigation and add testcases, fixing if the current
 behaviour of discarding empty components is incorrect.

-- 
Ticket URL: <http://bugs.call-cc.org/ticket/396>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.