Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 67439 invoked from network); 2 Oct 2002 07:13:00 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Oct 2002 07:13:00 -0000 Received: (qmail 5025 invoked by uid 97); 2 Oct 2002 07:13:48 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 5004 invoked by uid 97); 2 Oct 2002 07:13:47 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 4992 invoked by uid 98); 2 Oct 2002 07:13:47 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-Id: <5.1.1.6.2.20021001235628.00bbb108@mail.harbornet.com> X-Sender: caraunltd@mail.harbornet.com X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 02 Oct 2002 00:12:20 -0700 To: "Tomcat Developers List" From: micael Subject: Re: Tomcat 4.1.12 and Servlet Access 404 Errors: BUG? One Last Assurance In-Reply-To: <3D9A5965.2AA25A48@xn.com.au> References: <5.1.1.6.2.20021001192157.00b414d0@mail.harbornet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N So I can understand, where is the difference in the code between Tomcat 4.1.10 and 4.1.12? And, do you mean that servlet mappings rather than being generic to some "servlet/*" path be individualized? At 12:26 PM 10/2/2002 +1000, you wrote: >micael wrote: > > > > I cannot access a webapp with the normal > > http://localhost:8080/myapp/servlet/mydirectory.MyServlet with Tomcat > > 4.1.12. (Also, the embedded Tomcat 4.1.12 in JBoss 3.0.3 runs fine except > > that it won't access the examples servlets.) The error shown is a 404 "The > > requested resource (/myapp/servlet/mydirectory.MyServlet) is not > > available.". The same thing runs fine with Tomcat 4.1.0., both with and > > without JBoss. Is this a BUG in Tomcat 4.1.12, or are there new > > constraints on reaching servlets from outside the container in 4.1.12? > > > >For security reasons (see the release notes for details), the invoker >servlet is disabled by default now. This servlet is what makes >/webapp/servlet/... paths invoke the given servlet. It's recommended >that you give explicit servlet definitions and mappings in the webapps's >web.xml instead. > >Michael > >-- >To unsubscribe, e-mail: >For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: