tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hughes, Tim" <tim.hug...@cgey.com>
Subject RE: has anyone ever got the <error-page> feature (defined in web. xml) to work?
Date Thu, 05 Jul 2001 13:16:14 GMT
Hi,

I have been playing around with this for a couple of hours now and it seems
that the following is the case:

If the error is generated by a servlet (response.sendError(int i)), then:
-you can "catch" it with another servlet (i.e. with a servlet as error page)
-but you cannot "catch" it with a simple html file.

If the error is an HTTP error (e.g. you try to access a resource that
doesn't exist: error code 404):
-you cannot "catch it" at all: neither with a servlet or an html file.

Does anyone have any evidence of this being false? It would be nice if it
was.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tim Hughes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



-----Original Message-----
From: Randy Layman [mailto:randy.layman@aswethink.com]
Sent: 5. juli 2001 14:03
To: tomcat-user@jakarta.apache.org
Subject: RE: has anyone ever got the <error-page> feature (defined in
web. xml) to work?



	We have is successfully working for catching Java Exceptions.
Haven't tried HTTP Error codes, though.

	Randy

> -----Original Message-----
> From: Hughes, Tim [mailto:tim.hughes@cgey.com]
> Sent: Thursday, July 05, 2001 8:38 AM
> To: 'tomcat-user@jakarta.apache.org'
> Subject: RE: has anyone ever got the <error-page> feature (defined in
> web. xml) to work?
> 
> 
> 
> Hi,
> 
> We are trying to use the <error-page> facility but without 
> any success. Does
> Tomcat implement this or not?
> Has anyone seen it working?
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Tim Hughes
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> 
> 
> -----Original Message-----
> From: guido.bartels@gerling.de [mailto:guido.bartels@gerling.de]
> Sent: 4. juli 2001 17:27
> To: tomcat-user@jakarta.apache.org
> Subject: AW: http errors
> 
> 
> Hi Tim,
>  
> I tried the stuff you described, but had not success with it.
> I placed the error-page item in both web.xml files, but 
> nothing changed.
>  
> In addition I removed the <login-config> from the web-app 
> web.xml file and
> placed that section into the default web.xml.
> The result was, that the login-config seemed to be lost.
>  
> So what's wrong? I use Tomcat 3.2.2.
>  
> It seems to me, that Tomcat does not implement the specification!
>  
> Kind regards
> Guido
> 
> -----Ursprüngliche Nachricht-----
> Von: Hughes, Tim [mailto:tim.hughes@cgey.com]
> Gesendet am: Mittwoch, 4. Juli 2001 09:39
> An: 'tomcat-user@jakarta.apache.org'
> Betreff: RE: http errors
> 
> Hi,
>  
> You will find a full copy of the **default** web.xml in 
> TOMCAT_HOME/conf/.
>  
> What is the default web.xml --> Extract from the user guide 
> (which you will
> find at TOMCAT_HOME\doc\uguide\tomcat_ug.html: recommended reading)
> [A detailed description of web.xml and the web application structure
> (including directory structure and configuration) is 
> available in chapters
> 9, 10 and 14 of the  <http://java.sun.com/products/servlet/> 
> Servlet API
> Spec and we are not going to write about it. 
> 
> There is however a small Tomcat related "feature" that is related to
> web.xml. Tomcat lets the user define defaultw eb.xml values 
> for all context
> by putting a default web.xml file in the conf directory. When 
> constructing a
> new Context, Tomcat uses the default web.xml file as the base 
> configuration
> and the application specific web.xml (the one located in the 
> application's
> WEB-INF/web.xml), only overwrite these defaults.]
> 
> So if you want the error pages to apply to all webapps then 
> you put the
> error page tags in the default web.xml like this:
> 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> 
> <!DOCTYPE web-app
> 
> PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
> 
> "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
> 
> <web-app>
> 
> <!-- IMPORTANT: all the tags that were already in the default 
> web.xml file
> should remain in the file -->
>  
> <error-page>
> <exception-type>javax.servlet.TryagainException</exception-type>
> <location>/errors/TryAgain.html</location>
> </error-page>
>  
> <error-page>
> <error-code>503</error-code>
> 
> <location>/errors/TryAgain.html</location>
> </error-page>
> 
> </web-app>
> 
> (I assume that you have renamed the directories and files accordingly:
> errors directory and TryAgain.html file are only examples).
> 
> If you only want the error pages to apply to a particular 
> webapp then you
> should create a web.xml file that you place in
> TOMCAT_HOME/webapps/yourWebApp/WEB-INF. This file should look 
> like this:
> 
> <!DOCTYPE web-app
> 
> PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
> 
> "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
> 
> <web-app>
> 
> <error-page>
> <exception-type>javax.servlet.TryagainException</exception-type>
> <location>/errors/TryAgain.html</location>
> </error-page>
>  
> <error-page>
> <error-code>503</error-code>
> 
> <location>/errors/TryAgain.html</location>
> </error-page>
> 
> </web-app>
> 
> I hope this works.
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> Tim Hughes 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> 
> -----Original Message-----
> From: Francisco Areas Guimaraes [mailto:fareas@larc.usp.br]
> Sent: 4. juli 2001 02:25
> To: tomcat-user@jakarta.apache.org
> Subject: Re: http errors
> 
> 
> it didn´t work...could you please give a "complete" web.xml? and where
> should I put this file? in %TOMCAT_HOME%/conf or somewhere 
> else? I´m using
> tomcat 3.2.2 and win2k, I would like any help you could 
> provide, because I
> just started working with tomcat.
>  
> thanks,
>  
> Francisco
> fareas@larc.usp.br <mailto:fareas@larc.usp.br> 
> 
> ----- Original Message ----- 
> From: Hughes,  <mailto:tim.hughes@cgey.com> Tim 
> To: 'tomcat-user@jakarta.apache.org'
> <mailto:'tomcat-user@jakarta.apache.org'>  
> Sent: Tuesday, July 03, 2001 4:29 AM
> Subject: RE: http errors
> 
> Hi,
>  
> Using <error-page> elements in the web.xml, you can program 
> web applications
> to handle HTTP errors and exceptions.
>  
> The deployment description below makes the container send the
> /errors/TryAgain.html file if either a TryAgainExeption or the
> HttpServletResponse.SC_SERVER_UNAVAILABLE error code occurs:
>  
> <web-app>
>  
> <!-- Servlet definitions -->
>  
> <error-page>
> <exception-type>javax.servlet.TryagainException</exception-type>
> <location>/errors/TryAgain.html</location>
> </error-page>
>  
> <error-page>
> <error-code>503</error-code>
> 
> <location>/errors/TryAgain.html</location>
> </error-page>
>  
> I hope this helps.
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> Tim Hughes 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> 
> -----Original Message-----
> From: Francisco Areas Guimaraes [mailto:fareas@larc.usp.br]
> Sent: 3. juli 2001 02:15
> To: Lista tomcat User
> Subject: http errors
> 
> 
> Anyone know if I can set tomcat to use a custom page for http 
> errors, like
> 500, instead of it´s default???
>  
> please, help me, i´ve tried a lot of things and it didn´t help.
>  
> []´s
> Francisco
> 
> 
> 
> This message contains information that may be privileged or 
> confidential and
> is the property of the Cap Gemini Ernst & Young Group. It is 
> intended only
> for the person to whom it is addressed. If you are not the intended
> recipient, you are not authorized to read, print, retain, 
> copy, disseminate,
> distribute, or use this message or any part thereof. If you 
> receive this
> message in error, please notify the sender immediately and 
> delete all copies
> of this message.
> 
> 
> 
> 
> This message contains information that may be privileged or 
> confidential and
> is the property of the Cap Gemini Ernst & Young Group. It is 
> intended only
> for the person to whom it is addressed. If you are not the intended
> recipient, you are not authorized to read, print, retain, 
> copy, disseminate,
> distribute, or use this message or any part thereof. If you 
> receive this
> message in error, please notify the sender immediately and 
> delete all copies
> of this message.
> 
> 
> 
> 
> 
> --------------------------------------------------------------
> --------------
> -------
> This message is intended for the adressee or its 
> representative only. Any
> form of unauthorized use, publication, reproduction, copying 
> or disclosure
> of the content of this e-mail is not permitted. If you are 
> not the intended
> recipient of this e-mail message and its contents, please 
> notify the sender
> immediately and delete this message and all its attachments 
> subsequently.
> 
> 
> 
> This message contains information that may be privileged or 
> confidential and is the property of the Cap Gemini Ernst & 
> Young Group. It is intended only for the person to whom it is 
> addressed. If you are not the intended recipient, you are not 
> authorized to read, print, retain, copy, disseminate, 
> distribute, or use this message or any part thereof. If you 
> receive this message in error, please notify the sender 
> immediately and delete all copies of this message.
> 


This message contains information that may be privileged or confidential and is the property
of the Cap Gemini Ernst & Young Group. It is intended only for the person to whom it is
addressed. If you are not the intended recipient, you are not authorized to read, print, retain,
copy, disseminate, distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all copies of this message.

Mime
View raw message