Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 34503 invoked by uid 500); 5 Jul 2001 00:37:16 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 34494 invoked from network); 5 Jul 2001 00:37:16 -0000 From: "Marc Saegesser" To: Subject: RE: Tomcat 3.2.2 and Error page 404 Date: Wed, 4 Jul 2001 19:37:19 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <20010704131414.A9301@greenhydrant.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N This has already been fixed in 3.2.3-dev. Try the latest nightly build. > -----Original Message----- > From: David Rees [mailto:dbr@greenhydrant.com] > Sent: Wednesday, July 04, 2001 3:14 PM > To: tomcat-dev@jakarta.apache.org > Subject: Re: Tomcat 3.2.2 and Error page 404 > > > On Wed, Jul 04, 2001 at 11:53:05AM -0700, Renato Weiner wrote: > > > > Hi all, > > I know this has been discussed, but I can't find an ultimate > answer on this topic. I'm running Tomcat 3.2.2, I have latest the > StaticInterceptor.java from CVS. If I configure my web.xml with a > dynamic 404 error ( let's sat 404.jsp ) that doesn't exist, I got > an endless loop: > > > > 2001-07-04 02:10:17 - Ctx( ....: ): 404 R( + /servlet/xxx + > null) JSP file not found > > > > 2001-07-04 02:10:17 - Ctx( ....: ): Get real path /404.jsp > /home/client1/404.jsp /home/client1 > > > > 2001-07-04 02:10:17 - Ctx( ....: ): Get real path /404.jsp > /home/client1/404.jsp /home/client1 > > > > 2001-07-04 02:10:17 - Ctx( ....: ): Get real path /404.jsp > /home/client1/404.jsp /home/client1 > > > > Do anybody has a solution for this ? > > I have hit this myself. The only solution is to make sure that > the error pages you > define in face do exist. I haven't had time to look into root > cause of this myself, but > I'm not familiar with the Tomcat source anyway... > > -Dave