Bart, I just created a directory/file: http://zmbh.com/+plusdir/+plusfile
Seems to work, no encoding. I would think that urlencoding shouldn't be a problem because each url part has separate rules. http://www.ietf.org/rfc/rfc2396.txt might have more info. The question is if the plus sigh is a reserved character in the path component of a url: 3.3. Path Component The path component contains data, specific to the authority (or the scheme if there is no authority component), identifying the resource within the scope of that scheme and authority. path = [ abs_path | opaque_part ] path_segments = segment *( "/" segment ) segment = *pchar *( ";" param ) param = *pchar pchar = unreserved | escaped | ":" | "@" | "&" | "=" | "+" | "$" | "," The path may consist of a sequence of path segments separated by a single slash "/" character. Within a path segment, the characters "/", ";", "=", and "?" are reserved. Each path segment may include a sequence of parameters, indicated by the semicolon ";" character. The parameters are not significant to the parsing of relative references. I'm not sure if this means a '+' should be escaped or not. tom jackson On Mon, 2004-01-26 at 15:02, Bart Teeuwisse wrote: > Jim, > > you hit the nail on the head. http://dev.thecodemill.biz/%2Btest/ does > return a directory listing. But can the server ensure that clients will > encode plus signs? Or can AOLserver determine when to replace + with a space > and when to leave as is? > > /Bart > > > -- > 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. > -- 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.
