Thanks Andy,
http://www.w3.org/Addressing/rfc1738.txt
http://www.w3.org/Addressing/URL/uri-spec.html
In both the URI and URL BNF, + seems to be a legitimate path forming character.
There's nothing to suggest it's implementation dependent.
-Original Message-
From: Andy Bailey [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 05, 2001 10:14 AM
To: [EMAIL PROTECTED]
Subject: RE: Tomcat URL Problem
Hi Ross,
if you want to use + signs in a URL (inadvisable really) then you will
need to encode them such that the + sign is converted
to its %XXX equivalent. The + sign is used to denote spaces in GET
method URL's so it would appear that Tomcat is doing the right thing.
Use the - sign instead, or the _ (underscore) sign.
Andy Bailey
PS not being totally conversant with the relevant RFC's I am not 100%
certain of the above explanation however I personally avoid + signs in
URL's like the plague.
-Original Message-
From: Ross Allard [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 05, 2001 2:45 PM
To: '[EMAIL PROTECTED]'
Subject: Tomcat URL Problem
We have a tool which generates a website which, as usual, consists of a
directory tree of html and other files. Our file naming convention
makes heavy use of the plus sign, +, as a separator. E.g. file0+1,
file1+2. This apparently causes an error when deployed on Tomcat.
The plus sign seems to be mapped to space resulting in a 404 error. It
is our understanding that our naming scheme is fully w3c compliant and
we've had no problems with other html servers. Is this a Tomcat bug?
Any help would be appreciated.
Regards,
Ross Allard
Sas Institute
