"A string containing only the ’/’ character indicates the "default" servlet of the application. In this case the servlet path is the request URI minus the context path and the path info is null."
As for "images/foo.gif", this is translated to /images/foo.gif (or whatever the relative context is) by the web client.
EVERY valid HTTP reques starts with a / and is followed by something. If not, you may see the following:
=============== [EMAIL PROTECTED]: telnet ralph 80 Trying 198.168.0.1... Connected to 198.168.0.1. Escape character is '^]'. GET wookie HTTP/1.1 Host: what.ralph.bent.com Connection: close
HTTP/1.1 400 Bad Request Date: Thu, 21 Aug 2003 18:09:11 GMT Server: Apache/1.3.26 (Unix) mod_gzip/1.3.19.1a mod_jk/1.2.1 Connection: close Transfer-Encoding: chunked Content-Type: text/html; charset=iso-8859-1 ...
===============
-Tim
Mike Curwen wrote:
Actually, isn't "/" the default servlet ? "/*" would be "every
request", but just a single slash is 'when you don't recognize a
request, try this servlet'. Do you think <img src="images/foo.gif"> would work? (no leading / on
the image path)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
