If you're using Tomcat in stand-alone, as an HTTP server, that's what will happen. However, the original poster is using Apache + Tomcat, in which case Tomcat would return a 500 via the connector, not a 404. At least, that's what has happened in my experience.
John > -----Original Message----- > From: M [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 10, 2002 5:05 AM > To: Tomcat Users List > Subject: Re: Advice please: Apache doesn't seem to resolve Tomcat > symboliclinks > > > "Turner, John" wrote: > > > > True, but the symlinks, according to the original post, > work fine in Tomcat > > Standalone. If it was a Tomcat issue, it wouldn't throw an > Apache 404, it > > would throw a 500. 404 is not found, so that leads me to > believe that the > > paths in the logs for those URLs are not valid as far as WebApp is > > concerned. > > Well I was getting 404's in the logs with tomcat 4.1.12 using > sym links > and not 500 errors... until I upgraded then I got the file... > > -- > Regards, > M > > Martin Sillence > PR Newswire > > DL +44 (0)1865 78 5065 > F +44 (0)1865 78 5100 > W www.prnewswire.eu.com > --------------------------------------- > Any views or opinions are solely those of the author and do not > necessarily represent those of PR Newswire Europe. The e-mail > contents are intended only for addressee and may contain > confidential and/or privileged material. If you are not the > intended recipient, please do not read, copy, use or disclose > this communication and notify the sender. > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
