Hi, Eh... seems that we do still have some (compat) problems there...
I do not doubt that the current implementation in urlencode.c is OK, but we do have many existing installations running on the AOLserver and a couple of new ones running with NaviServer now. There are subtle differences in way the urldecoder works. The naviserver one will not expand "a+b" into "a b" if walking over the path part. This seems to be correct. But the AOLserver urlencoder encodes the " " in both url path part *and* the query part with "+". Therefore we now have a problem when operating between the Naviserver and Aolserver instances. We are now stucked. Question: is there an easy way to #ifdef parts of the code so the encoding/decoding machinery becomes compatible to the aolserver one? I will need those compat switches until we get all our customers (and they all their instances) updated. This can take some considerable time, though, perhaps a year or so. I have been walking over the sources and there seems to be quite a few changes in this respect in various parts of the code. In order to save some (electronic archeology) time I thought I'd rather ask here. Stephen, do you have some idea how I can achieve this? Thanks, Zoran
