[Chicken-janitors] Re: #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                                  
 
Resolution:              |    Keywords:  uri, pedantic strictness, rfc, 
standards
-------------------------+--------------------------------------------------

Comment(by iraikov):

 I meant the discarding-of-empty-path-segments behavior. Some actual test
 cases that illustrate why this is a problem. Now that I think about it,
 SMB file sharing URIs are also very insistent about keeping a large number
 of consecutive slashes, so I would not be surprised if the current uri-
 generic breaks those. And as I wrote this, I just realized that the uri-
 generic test cases do not include any SMB URIs, so we need to fix this,
 regardless of the outcome of this ticket.

 It does sound like keeping the empty path segments would be a sane
 behavior. Backward compatibility should not be a big issue, if any user of
 the library wanted to write their own normalization procedure that removes
 the empty segments, they can call update-uri and filter the path
 accordingly.

 Replying to [comment:5 sjamaan]:
 >
 > Which behaviour do you mean?
 >
 > I just spent an hour implementing a nasty workaround to encode empty
 path components for a >project at work because Apache discards empty path
 components. It would be nice if our implementation kept them around.

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