On Monday 21 February 2005 17:18, Dossy Shiobara wrote: > What makes this even more frustrating is that the best solution to this > problem isn't simple. It might be made simpler by decoupling the URL > decoding code that AOLserver uses when parsing request URLs from the > code that powers ns_urlencode/ns_urldecode. This way, the server can > easily Do The Right Thing(tm) when parsing request URLs, independently > of all the problems we'll have changing the behavior of > ns_urlencode/ns_urldecode with regards to backwards compatibility.
Yes, decouple the code. Regardless of how the Tcl procs are being used, the server needs to parse the url correctly. My understanding is that any character can be sent in escaped form. The entire uri is considered escaped. This fact allows you to get files which contain a '+' by substituting a %2b. The only issue is that the decoding procedure incorrectly transforms a '+' in the path to a space. However it also accepts spaces in the url. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
