Am 11.05.2005 um 14:12 schrieb Stephen Deasey:
You'll have a syncronization problem: you'll have to throw the switch on all servers at the same time.
Imagine: there are about 500 installations world-wide we have currently. So, this one is not an option...
Another alternative might be to patch the AOLserver instances to always encode spaces as %20, which is always valid. Then you only need to ensure that you don't install naviserver on a network with an unpatched AOLserver.
Again not an option...
Oh, I guess you'd still have to patch naviserver to also encode using %20, but at least that's a valid encoding.
Ehm... what I found out is that the "+" sign should be "accepted" by the Naviserver as one of the valid escaped ' ' chars. So, I have added URLDECODE_RELAXED (undefined by default) in the UrlDecode() so the things encoded as '+'s will be converted to ' 's even when walking the *path* part of the url (because this is how the aolserver would encode the string). Now, I understand this ain't very clean but it help us for now. I will remove this define when we complete the transition at the customer sites. Anyways, it should not hurt anybody I believe. Zoran
