> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Eric B.
> Subject: Re: Custom 404 for non-existant contexts?
>
> Would just modifying the ROOT/WEB-INF/web.xml work?
It should, since any unmatched context paths are given to the default
app for processing (and usually a 40
> |>>
> |>> Is there a way to create a custom 404 error page for Tomcat
> |>> for non-existant context paths?
> |
> |> What happens if you declare a custom error page for the ROOT (default)
> |> webapp?
> |
> | Yeah - that's pretty much the only thing I managed to figure out. I
> updated
> | the c
you;d have to custom do it
http://people.apache.org/~fhanik/covalent-error-report-valve.jar
Filip
Eric B. wrote:
Is there a way to create a custom 404 error page for Tomcat for non-existant
context paths?
I know how to create a custom 404 error page within my application, but am
running int
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric,
Eric B. wrote:
| "Caldarale, Charles R" <[EMAIL PROTECTED]> wrote in message
|
news:[EMAIL PROTECTED]
|>> Subject: Custom 404 for non-existant contexts?
|>>
|>> Is there a way to create a custom 404 error page for Tomcat
|>> for non-existant co
"Caldarale, Charles R" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>> Subject: Custom 404 for non-existant contexts?
>>
>> Is there a way to create a custom 404 error page for Tomcat
>> for non-existant context paths?
>What happens if you declare a custom error page for the ROOT (
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Eric B.
> Subject: Custom 404 for non-existant contexts?
>
> Is there a way to create a custom 404 error page for Tomcat
> for non-existant context paths?
What happens if you declare a custom error page for the ROOT (default)
webapp?
- Chuck
