[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 sjamaan):

 None, that's the problem; it is suspiciously silent about it. See also the
 analysis of the Apache bugreport.

 Because the grammar allows empty paths (and our parser accepts it, which
 is fine), but the RFC does not mention any normalization or discarding of
 empty path components, it would be logical to keep empty path components
 around. It would also be a generalization of what we do with trailing
 slashes, so it might clean up our code too.

 I didn't create this ticket to complain; it was just a reminder for
 myself. If you want to handle it that's fine, but I intended to work on it
 later today or tomorrow.

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