Hi there, I am using tomcat 5.5 as an RTSP server, and I need to send
response codes back, but I do not need to send any HTML response back. I
know that I can change the response page that is returned by editing web.xml
and adding the following
error-page
error-code404/error-code
Hi Rob,
I have the same problem as you have.
I can tell you what I did but it is not as good as I want it to be.
Maybe others will help us with a better solution.
So I wrote SilentErrorValve.java. This is insufficient because one has
to have a response otherwise (in my case with apache httpd amd
/show_bug.cgi?id=29620
Error Pages Aren't Run Through Filters
--- Additional Comments From [EMAIL PROTECTED] 2004-06-18 17:35 ---
Yes, it works fine (The Servlet Tcks has a couple of tests like that). Please
follow up on tomcat-users.
Thanks
-- Jeanfrancois
You have received this email for one of two reasons. One is that you or someone with
your email address in their address book is infected with an email virus, and this
virus was emailed to me.
The other reason could be that you legitimately tried to contact me through
/show_bug.cgi?id=29620
Error Pages Aren't Run Through Filters
Summary: Error Pages Aren't Run Through Filters
Product: Tomcat 5
Version: 5.0.25
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
/show_bug.cgi?id=29620
Error Pages Aren't Run Through Filters
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
/show_bug.cgi?id=29620
Error Pages Aren't Run Through Filters
--- Additional Comments From [EMAIL PROTECTED] 2004-06-16 18:31 ---
Ah... that would explain it. Sorry for the trouble. Looks like I need to get
better references. Thanks very much for the tip
/show_bug.cgi?id=29620
Error Pages Aren't Run Through Filters
--- Additional Comments From [EMAIL PROTECTED] 2004-06-17 00:02 ---
After adding in dispatcherERROR/dispatcher, I still don't see the error page
being wrapped by the filter. I have just reviewed the spec, too. Here are my
configs
/show_bug.cgi?id=29583
Filters not invoked on error pages
Summary: Filters not invoked on error pages
Product: Tomcat 4
Version: 4.1.24
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
/show_bug.cgi?id=29583
Filters not invoked on error pages
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
/show_bug.cgi?id=29583
Filters not invoked on error pages
--- Additional Comments From [EMAIL PROTECTED] 2004-06-15 19:09 ---
OK for the 2.4 specification and Tomcat 5, for the filters configuration that
2.3 specification doesn't address.
But, why change the initial request and replace
/show_bug.cgi?id=29505
Tomcat returns HTTP 500 when I use the JSP error pages mechanism
Summary: Tomcat returns HTTP 500 when I use the JSP error pages
mechanism
Product: Tomcat 5
Version: 5.0.25
Platform: PC
OS/Version: Windows XP
/show_bug.cgi?id=29505
Tomcat returns HTTP 500 when I use the JSP error pages mechanism
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=28465
Cannot use jsp error pages from servlets
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution
/show_bug.cgi?id=28465
Cannot use jsp error pages from servlets
--- Additional Comments From [EMAIL PROTECTED] 2004-04-20 10:24 ---
You don't agree with what? Do you mean that it's not common to set those
attributes or that the pet store is not implemented correctly
/show_bug.cgi?id=28465
Cannot use jsp error pages from servlets
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
/show_bug.cgi?id=28465
Cannot use jsp error pages from servlets
--- Additional Comments From [EMAIL PROTECTED] 2004-04-20 13:30 ---
I don't see anything difficult to understand: I understand your use case, and I
consider it invalid
/show_bug.cgi?id=28465
Cannot use jsp error pages from servlets
Summary: Cannot use jsp error pages from servlets
Product: Tomcat 5
Version: 5.0.19
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Major
Priority
/show_bug.cgi?id=28465
Cannot use jsp error pages from servlets
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
/show_bug.cgi?id=6659
HttpUtils.getRequestURL gives incorrect URL with web.xml redirected error pages
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW
Hi , the next question is bothering me:
I want to have custom error pages for my webapp.
Well this works:
(web.xml of Tomcat)
error-page
error-code500/error-code
location/server_error.html/location
/error-page
error-page
error-code404/error-code
location/file_not_found.html/location
/error
/show_bug.cgi?id=12978
Tomcat doesn't pick up error pages.
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
/show_bug.cgi?id=12978
Tomcat doesn't pick up error pages.
--- Additional Comments From [EMAIL PROTECTED] 2002-09-27 18:30 ---
Created an attachment (id=3270)
o.a.c.v.ErrorDispatcherValve patch
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto
/show_bug.cgi?id=12978
Tomcat doesn't pick up error pages.
--- Additional Comments From [EMAIL PROTECTED] 2002-09-27 18:33 ---
This patch should fix your problems.
the valve was never handling ServletException when looking for errorpages.
see SRV.9.9.2
--
To unsubscribe, e-mail: mailto
/show_bug.cgi?id=12978
Tomcat doesn't pick up error pages.
--- Additional Comments From [EMAIL PROTECTED] 2002-09-27 18:42 ---
Created an attachment (id=3271)
o.a.c.v.ErrorDispatcherValve newer patch
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail
/show_bug.cgi?id=12978
Tomcat doesn't pick up error pages.
--- Additional Comments From [EMAIL PROTECTED] 2002-09-27 18:44 ---
The second patch conforms to the spec.. the first still did things backwords..
quote
The web application may have declared error pages using the exception-type
/show_bug.cgi?id=12978
Tomcat doesn't pick up error pages.
--- Additional Comments From [EMAIL PROTECTED] 2002-09-27 18:47 ---
Created an attachment (id=3272)
o.a.c.v.ErrorDispatcherValve even newer.. one of those days
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional
/show_bug.cgi?id=12978
Tomcat doesn't pick up error pages.
Summary: Tomcat doesn't pick up error pages.
Product: Tomcat 4
Version: 4.1.12
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Minor
Priority: Other
/show_bug.cgi?id=12978
Tomcat doesn't pick up error pages.
--- Additional Comments From [EMAIL PROTECTED] 2002-09-24 22:24 ---
This seems to be the same thing that is happening in Bug #11091.
I don't know of a solution, but I do have a potential workaround that you could
try: If you change
/show_bug.cgi?id=12978
Tomcat doesn't pick up error pages.
--- Additional Comments From [EMAIL PROTECTED] 2002-09-24 22:58 ---
So something was broken b/w 4.0.4 and 4.1.x? I'm trying to migrate an
application from 4.0.4 - where everything works fine.
--
To unsubscribe, e-mail: mailto
/show_bug.cgi?id=6659
HttpUtils.getRequestURL gives incorrect URL with web.xml redirected error pages
--- Additional Comments From [EMAIL PROTECTED] 2002-06-07 14:55 ---
So... Does it make sence to just change the method
HttpUtils.getRequestURL( request )
so that it simply has 1
/show_bug.cgi?id=9252
Tomcat sometimes posts HTML Error Pages as text/plain instead of text/html.
Summary: Tomcat sometimes posts HTML Error Pages as text/plain
instead of text/html.
Product: Tomcat 4
Version: 4.0.3 Final
Platform: PC
/show_bug.cgi?id=9252
Tomcat sometimes posts HTML Error Pages as text/plain instead of text/html.
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW
/show_bug.cgi?id=6659
HttpUtils.getRequestURL gives incorrect URL with web.xml redirected error pages
[EMAIL PROTECTED] changed:
What|Removed |Added
Component|Unknown
/show_bug.cgi?id=6659
HttpUtils.getRequestURL gives incorrect URL with web.xml redirected error pages
Summary: HttpUtils.getRequestURL gives incorrect URL with web.xml
redirected error pages
Product: Tomcat 4
Version: 4.0.2 Final
Platform: PC
Hi,
Say a user has a custom error page for status codes of 500
when an uncaught exception occurs. The request parameter,
javax.servlet.error.status_code, is not set, so if the
error page tries to access this req. parameter, null will
be returned.
Attached is a patch that I've tested in my env
PROTECTED]]
Sent: Friday, June 01, 2001 12:04 AM
To: [EMAIL PROTECTED]
Subject: Re: Problem+Fix concerning static error pages in Tomcat 3.2.2
Hmm.. In fact (in 3.2.2 atleast), it does not even matter if the
file exists
or not, since the FileHandler simply uses the originally
requested file
Hmm.. In fact (in 3.2.2 atleast), it does not even matter if the file exists
or not, since the FileHandler simply uses the originally requested file and
StaticInterceptor. So I suppose its the same bug alltogether.
If things are fixed in 3.2.3, I'm happy enough though. The dirty fix I
posted
S. Heijnen [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 12:50 AM
To: [EMAIL PROTECTED]
Subject: Re: Problem+Fix concerning static error pages in Tomcat 3.2.2
I use virtual hosts, but don't think that is the cause, although
I have not
traced this down (I will check that aswell
PROTECTED]]
Sent: Wednesday, May 30, 2001 9:38 AM
To: [EMAIL PROTECTED]
Subject: RE: Problem+Fix concerning static error pages in Tomcat 3.2.2
Bloody hell.
This bug was fixed a couple months ago and then got whacked by a
late commit
to StaticInterceptor.java. I take partial responsibility
A related bug to this is a nasty stack overflow error if an error page that you
define is not found. It's pretty easy to reproduce, just add this to your
web.xml:
error-page
error-code404/error-code
location/some-nonexistant-file.jsp/location
/error-page
Then try to access a
I'm using Tomcat 3.2.2 (relase) and have configured static .html files as
error pages. We used JSP pages before, and everything was fine... However
since we're using static files, Tomcat will enter an infinite loop and
eventually crash with a stack overflow (with a good change of leaving Tomcat
Sorry, I made a mistake in my previous post. The fix we use is
'req.setServletPath( ctx.getPath() + / + errorPath )', and _not_
'req.setRequestURI( ctx.getPath() + errorPath )' as stated in my message.
Cheers,
Peer Heijnen
Could you please supply a sample webapp that demonstrates this? Static
error pages seem to work OK for me.
-Original Message-
From: Peer Heijnen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 29, 2001 5:52 AM
To: tomcat-dev
Subject: Problem+Fix concerning static error pages
will wrap up a webapp and post
the .war file.
- Original Message -
From: Marc Saegesser [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, May 29, 2001 8:54 PM
Subject: RE: Problem+Fix concerning static error pages in Tomcat 3.2.2
Could you please supply a sample webapp
is
supposed to return a handler for the given ctx, and does so by creating a
sub-request. The subrequest must be for the ctx - and the vhost is
required.
Costin
On Tue, 24 Apr 2001, Peer Heijnen wrote:
Hi,
We've been using Tomcat 3.2.1 quite succesfully, but ran into trouble with
error pages
To: Tomcat-Dev
Subject: HTTP Status Codes and Error Pages
I can't tell if this is a bug or intended behavior:
I have a servlet that acts as the error page for my
webapp. Note that this is
set up using the web.xml file, not the errorPage
directive in the JSPs (if that
makes any
:[EMAIL PROTECTED]]
Sent: Tuesday, March 06, 2001 9:51 AM
To: [EMAIL PROTECTED]
Subject: RE: HTTP Status Codes and Error Pages
Ethan,
You missed some good discussions on this two weeks ago
between Costin and myself! :-)
Not only is it (premature commit) caused by the
RequestDispatcher.include
Costin - were you going to make the changes
(out.flush() - out.flushBuffers()) in
JspParseEventListener.generateFooter() and
PageContextImpl.include() that we had discussed? I
had thought that you implied you were going to do it
(that was before I was a committer) but I just noticed
that
I can't tell if this is a bug or intended behavior:
I have a servlet that acts as the error page for my webapp. Note that this is
set up using the web.xml file, not the errorPage directive in the JSPs (if that
makes any difference?)
When there is an error (say 500 Internal Server Error), it
:03 PM
To: Tomcat-Dev
Subject: HTTP Status Codes and Error Pages
I can't tell if this is a bug or intended behavior:
I have a servlet that acts as the error page for my webapp. Note that this is
set up using the web.xml file, not the errorPage directive in the JSPs (if that
makes any difference
Hi ppl:
I had posted a very simple query..but had
not received any comments. So am i the only unlucky person who's stuck on this
simple problem. Any suggestions are welcome plz.
I want Custom error pages, in my application, the
two solutions i have is to use the "ErrorDoc
Hi everybody:
I using Apache and TomCat 3.2
and was trying the option of having customized error pages for the application.
Now for this as i need error pages corresponding to Exception's in my code i am
trying that option using the web.xml file.
But somehow am not being taken to the error
53 matches
Mail list logo
