Re: [Chicken-janitors] #998: uri->string / make-uri path encoding inconsistencies

[Chicken Trac]

#998: uri->string / make-uri path encoding inconsistencies
----------------------+-----------------------------------------------------
  Reporter:  andyjpb  |       Owner:  sjamaan 
      Type:  defect   |      Status:  accepted
  Priority:  major    |   Milestone:  someday 
 Component:  unknown  |     Version:  4.8.x   
Resolution:           |    Keywords:          
----------------------+-----------------------------------------------------

Comment(by sjamaan):

 Also note that the final "foo[]" vs "foo%5b%5d" example I gave proves that
 the current behaviour is at least as correct as can be given the
 circumstances: any random string used as a key in the query alist will be
 acceptable and interpreted as-is: the string "foo[]" will arrive on the
 server as "foo[]", rather than as "foo" indicating array notation (which
 is not what was intended).

 Of course, you're in trouble if you really *do* intend "foo[]" to end up
 in the final URI string as-is, but then you probably need to define your
 own layer over uri-generic which has this additional feature (it still
 needs to be able to encode the key "foo[]" as well as indicate the key
 "foo" needs to be an array).

 Not fully-decoding everything (and leaving it to the user) isn't an option
 either, because that convenience kind of is the whole point that uri-
 common even exists!

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