'true' and then try to
detect within your app, if the client provided a valid certificate and
redirect them to an error page if that is not the case.
Source: https://stackoverflow.com/a/46488689/1180010
+1
If the TLS handshake fails (because the certs are unacceptable to one
party
n your app, if the client provided a valid certificate and
redirect them to an error page if that is not the case.
Source: https://stackoverflow.com/a/46488689/1180010
Sebastian
On 06.02.2025 18:59, Peter Rader wrote:
Hi,
I have a website that use mutual authentication for over 100 perso
to have a custom website instead of the browser's
built-in error-page?
Kind regards
Peter Rader
--
Fachinformatiker AE / IT Software Developer
Peter Rader
Wilsnacker Strasse 17
10559 Berlin - GERMANY
Tel: 0049 (0)30 / 6 29 33 29 6
Fax: 0049 (0)30 / 6 29 33 29 6
Handy: 0049 (0)176 / 87 521 576
mething like a request attribute that could be included in a custom
error page for example.
However, the current Tomcat code for authentication is structured in
such a way that exposing the reason for an authentication failure would
require a reasonable amount of refactoring. I don't think an
?
>
> No.
>
> I do think there is an argument for providing information on the reason
> for the authentication failure via a mechanism that allows system
> administrators to decide if they want to pass it on to the users or not.
> Something like a request attribute that could be inc
ers or not.
Something like a request attribute that could be included in a custom
error page for example.
However, the current Tomcat code for authentication is structured in
such a way that exposing the reason for an authentication failure would
require a reasonable amount of refactoring. I don&
I know it has been asked dozens of times but the response is always "Cannot
be done in a standard way".
But why can't we change Tomcat to provide further details to the error page
of why the login failed?
I would have thought tomcat can support that easily without any backward
comp
On 24/09/2021 11:56, Jan Pernica wrote:
Hi
how can I easly create error page for the whole server? Curretly if I
add to conf/web.xml
500
/error/error.html
404
/error/error.html
And put into webapps/ROOT/error/error.html page it works
Hi
how can I easly create error page for the whole server? Curretly if I
add to conf/web.xml
500
/error/error.html
404
/error/error.html
And put into webapps/ROOT/error/error.html page it works only for ROOT
context. Other contexts shows
ed but the return was not worked.
发送自 Windows 10 版邮件应用
发件人: Mark Thomas
发送时间: 2018年8月6日 3:32
收件人: users@tomcat.apache.org
主题: Re: [Tomcat] Error page not work for 400 error.
On 05/08/2018 04:13, Leonard Afeng wrote:
> Dear all,
>
> I custom the error page in web.xml as below:
>
On 05/08/2018 04:13, Leonard Afeng wrote:
Dear all,
I custom the error page in web.xml as below:
And I added some log action in org.apache.catalina.util.ErrorPageSupport
and found out that in some case the 400 error page not working but the
default error page.
20:02:59.674 INFO
Dear all,
I custom the error page in web.xml as below:
400
/error400.html
404
/error404.html
java.lang.IllegalArgumentException
/error404.html
And I added some log action in org.apache.catalina.util.ErrorPageSupport
and found out that in some case the 400 error
> [...]
> > “It is implied but it could be clearer.”
>
> [...]
>
> I agree that default ErrorReportValve is not something that has to be
> backward compatible as the apps should have provided their own. Yet,
> we were using the default as it was working very well and was covering
> our needs.
>
> -Original Message-
> From: Mark Thomas
> Sent: 26 юли 2018 г. 19:04
> To: Tomcat Users List
> Subject: Re: HttpServletResponse.sendError - missing message in error page
>
> On 26/07/2018 13:46, Assia Djambazova wrote:
> > Hello,
>
me from the spec [2] that the message should
be displayed: *The server defaults to creating the response to look like an
HTML-formatted server error page containing the specified message, setting
the content type to "text/html"*
This is not a spec compliance issue. The ErrorReportValve
message should
> be displayed: *The server defaults to creating the response to look like an
> HTML-formatted server error page containing the specified message, setting
> the content type to "text/html"*
>
> I use the ErrorReportValve and showReport is set to false. Rea
E
I think that this change is the cause [1]
However, this change looks incompatible with servlet spec and breaks our
integration tests. It seems to me from the spec [2] that the message should
be displayed: *The server defaults to creating the response to look like an
HTML-formatted server error page
Mark
Thanks for taking the time to help. Again, I appreciate it.
cjb> We are getting dinged by a vulnerability scan for the default
cjb> not-found error page being returned by Tomcat for a Status 404.
cjb> [...]
cjb> And we're using Tomcat 6.0.37 (ahem).
MT> And you are wor
Leon, Mark, and Alejandro
Thanks for your time and suggestions. I appreciate it.
cjb> We are getting dinged by a vulnerability scan for the default
cjb> not-found error page being returned by Tomcat for a Status 404.
cjb> [...]
cjb> However, I can't find where the error-page f
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Wednesday, May 2, 2018 4:01 PM
To: users@tomcat.apache.org
Subject: Re: tomcat 6 vulnerability scan default error page help
> On 02/05/18 20:51, Leon Rosenberg wrote:
> > Hi Mark,
> >
> > I ag
tomcat\lib directory again.
Hope this could help you, I'm using Tomcat 8.0.27
"Berneburg, Cris J. - US" escribió:
We are getting dinged by a vulnerability scan for the default
not-found error page being returned by Tomcat for a Status 404.
On my dev server when requesting
t for.
Don't get me started on PCI compliance...
Oh, and Cris - take a look at the ErrorReportValve. That is where the
default error page is coming from.
Mark
>
> regards
> Leon
>
> On Wed, May 2, 2018 at 9:42 PM, Mark Thomas wrote:
>
>> On 02/05/18 20:27, Bernebu
wrote:
> On 02/05/18 20:27, Berneburg, Cris J. - US wrote:
> > We are getting dinged by a vulnerability scan for the default not-found
> error page being returned by Tomcat for a Status 404.
> >
> > On my dev server when requesting an invalid URL, Tomcat returns a Status
On 02/05/18 20:27, Berneburg, Cris J. - US wrote:
> We are getting dinged by a vulnerability scan for the default not-found error
> page being returned by Tomcat for a Status 404.
>
> On my dev server when requesting an invalid URL, Tomcat returns a Status 404
> page that disp
Hi Cris,
try to add following to your web.xml
404
/error404.html
regards
Leon
On Wed, May 2, 2018 at 9:27 PM, Berneburg, Cris J. - US wrote:
> We are getting dinged by a vulnerability scan for the default not-found
> error page being returned by Tomcat
We are getting dinged by a vulnerability scan for the default not-found error
page being returned by Tomcat for a Status 404.
On my dev server when requesting an invalid URL, Tomcat returns a Status 404
page that displays the Tomcat version. Right, I need to do something about
that.
However
Hi
I have a web application deployed on tomcat.
I have used custom login module of JAAS for authentication and provided
login and error page in web.xml.
I want to access message of login exception which I threw in login module
into error page - so that custom message can be displayed to user
ok. i see the light ..
Thanks a zillion! 😊
> Date: Tue, 19 May 2015 15:56:47 +0100
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: Tomcat valve JAAS : form error page displayed first before
> response reaches back to Tomcat valve
>
> On 19/05/201
On 19/05/2015 15:51, David kerber wrote:
> On 5/19/2015 10:46 AM, Kim Ming Yap wrote:
>>
>> You said ..
>>
>> "> Actually, the better analogy is that there is an application that can
>>> tell you whether or not 1+1=2, and you're asking it to explain why the
>>> numbers they entered don't total up t
any more information is just setting yourself up to be a
victim of much quicker brute-force attacks, because you're giving them
lots of help.
Date: Tue, 19 May 2015 10:34:48 -0400
From: dcker...@verizon.net
To: users@tomcat.apache.org
Subject: Re: Tomcat valve JAAS : form error page di
. i will ask 1+1 = 10?
That's the issue.
> Date: Tue, 19 May 2015 10:34:48 -0400
> From: dcker...@verizon.net
> To: users@tomcat.apache.org
> Subject: Re: Tomcat valve JAAS : form error page displayed first before
> response reaches back to Tomcat valve
>
> On 5/19/201
etc.
That's why when i started looking at this issue, well lots of complaints on
this. Just google it.
Just my thoughts.
Date: Tue, 19 May 2015 09:10:57 -0400
From: ch...@christopherschultz.net
To: users@tomcat.apache.org
Subject: Re: Tomcat valve JAAS : form error page displayed first
> Subject: Re: Tomcat valve JAAS : form error page displayed first before
> response reaches back to Tomcat valve
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Ming Yap,
>
> (Please let me know if I'm using your given name properly... you
> haven
hristopherschultz.net To: users@tomcat.apache.org Subject:
>> Re: Tomcat valve JAAS : form error page displayed first before
>> response reaches back to Tomcat valve
>>
> Ming Yap,
>
> On 5/18/15 4:56 PM, Kim Ming Yap wrote:
>>>> Now here's come
good question.lol
l...@bsoft.com.cn
From: Kim Ming Yap
Date: 2015-05-19 06:23
To: Tomcat Users List
Subject: RE: Tomcat valve JAAS : form error page displayed first before
response reaches back to Tomcat valve
I think Tomcat should provide interfaces for different scenarios .. that'
t; From: ch...@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: Tomcat valve JAAS : form error page displayed first before
> response reaches back to Tomcat valve
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Ming Yap,
>
> On 5/18/15 4:56 PM, Ki
> This message propagate to error page4. Invalid password ->
> This message propagate to error page
You should do some reading about user-enumeration vulnerabilities and
similar things. You probably don't want to give this kind of
information to a user. Hint: the user might be an adv
Invalid password -> This message propagate to error page
There's no way to propagate the above error messages to the error page from
JAAS login module since this module has no access to those important
aforementioned objects.
Hence i turn to valve (storing ThreadLocal). But as you can see
check to see if the response has been committed, but you can't
do anything effective to stop it.
- -chris
>> Date: Mon, 18 May 2015 14:54:24 +0100 From: ma...@apache.org To:
>> users@tomcat.apache.org Subject: Re: Tomcat valve JAAS : form
>> error page displayed first
You said
"The error page will be handled by the webapp or the ErrorReportingValve - both
of whichh may get called before your Valve depending on how the Valve is
configured."
How do i ensure that my custom valve is called before the the
ErrorReportingValve?Is there some settings
flow?
> Date: Mon, 18 May 2015 14:54:24 +0100
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: Tomcat valve JAAS : form error page displayed first before
> response reaches back to Tomcat valve
>
> On 18/05/2015 13:57, Kim Ming Yap wrote:
> >
ow ..
>
> Gee .. i got this wrong all the while
> Think i'm seeing the light ..
Happy to help.
Mark
>
>
>> Date: Mon, 18 May 2015 13:43:14 +0100
>> From: ma...@apache.org
>> To: users@tomcat.apache.org
>> Subject: Re: Tomcat valve JAAS : form
low ..
Gee .. i got this wrong all the while
Think i'm seeing the light ..
> Date: Mon, 18 May 2015 13:43:14 +0100
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: Tomcat valve JAAS : form error page displayed first before
> response reaches back to To
nal objects)
the Authenticator calls the filter.
Neither the request nor the response are part of the processing chain.
They are objects that are passed up and down the chain.
> If invalid credential ..
>
> request --> valve --> JAAS --> response --> valve (break point and s
ced the flow exactly as indicated on
my email (I've traced is using system.out.println)
request --> valve --> JAAS --> filter --> JSP --> response --> filter --> JAAS
--> valve --> browser
If invalid credential ..
request --> valve --> JAAS --> response
> flow of JAAS back to the client should the form based authentication failed.
> SOFTWARE:1. Apache Tomee plus 1.7.12. Java 83. Tomcat JAAS Realm
> OBJECTIVE:Custom error captured in JAAS login module to propagate to error
> page
You are unlikely to get much help from Tomcat with this
Thought of adding this custom error as an attribute in the session
object.However I noticed that the error page is already displayed before i
could add this cusom error (immediately after the getNext method).Due to that
the ready custom error message cannot be usedSAMPLE CODES:1. web.xml
authentication failed.
SOFTWARE:1. Apache Tomee plus 1.7.12. Java 83. Tomcat JAAS Realm
OBJECTIVE:Custom error captured in JAAS login module to propagate to error page
BASIC UNDERSTANDING:
The Tomcat JAAS layer is not integrated with the web container layer. Hence the
former does not have access to r
st is made for a file that does not exist. Since the file doesn't
exist, I actually wanted to show a proper 404 error page matching the error
pages for the rest of my server. Currently, all I see is a blank page from
the CGIServlet since my debug level doesn't meet the logging condition.
2015-03-16 21:52 GMT+03:00 Jacob Haverkost :
> Version: 6.0.43
> OS: Win7 x64
>
> Currently, the CGIServlet does not appear to support using the 404
> error-page specified in the web.xml (ROOT). The error-pages work fine
>
> This appears to be due to the line, res.setStatus(4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jacob,
On 3/16/15 2:52 PM, Jacob Haverkost wrote:
> Version: 6.0.43 OS: Win7 x64
>
> Currently, the CGIServlet does not appear to support using the 404
> error-page specified in the web.xml (ROOT). The error-pages work
> fine
>
Version: 6.0.43
OS: Win7 x64
Currently, the CGIServlet does not appear to support using the 404
error-page specified in the web.xml (ROOT). The error-pages work fine
This appears to be due to the line, res.setStatus(404);, inside of doGet().
According to the documentation for
On 19/08/2014 21:05, Mark Haroldson wrote:
> Is there a way to route all errors to a single web page?
Leave out the error-code tag and you define the default error page.
That will work in Tomcat 8 and I think in 7 as well.
Mark
>
>
>
>
>
> Something like:
Is there a way to route all errors to a single web page?
Something like:
all
myerror.jsp
Basically I want to control the content of everything that goes out of my
service.
Thanks
Mark
wrote:
> >>
> >> Hello,
> >>
> >> We are using Tomcat to host a number of web applications as a
> >> uniform solution. We trying to implement something that seems to
> >> be an odd requirement, evh it is really a use case for us.
> >>
&g
olution. We trying to implement something that seems to
>> be an odd requirement, evh it is really a use case for us.
>>
>> We would like to define a single [default] error page for all
>> web applications residing on this Tomcat instance. After some
>> experimentat
; We would like to define a single [default] error page for all web
> applications residing on this Tomcat instance. After some experimentation
> and googling around, it seems that there is no clear-cut solution for
this.
> I see a few options;
>
> - Let the global conf/web.xml defi
Hello Serge,
Thank you for your reply. This option seems to be similar to the first
thing i tried, editing conf/web.xml. As is suggested in
http://stackoverflow.com/questions/13914575/how-to-build-server-level-custom-error-page-in-tomcat
But contrary to what's stated in the stackoverlow me
Hello Maarten,
When I was in the same boat, I found
http://stackoverflow.com/questions/13914575/how-to-build-server-level-custom-error-page-in-tomcatand
http://wiki.apache.org/tomcat/FAQ/Miscellaneous#Q6 both very helpful.
I found these by googling
https://www.google.nl/?gws_rd=cr&am
Hello,
We are using Tomcat to host a number of web applications as a uniform
solution. We trying to implement something that seems to be an odd
requirement, even though it is really a use case for us.
We would like to define a single [default] error page for all web
applications residing on this
David Kerber wrote:
On 11/30/2012 5:59 PM, André Warnier wrote:
Christopher Schultz wrote:
...
I've even seen a site with a Perl-based (or was it PHP-based) service
..
must have been PHP, not Perl, I'm sure. We Perl guys don't do things
that way.
As I was telling Leo off-line, we have a nic
On 11/30/2012 5:59 PM, André Warnier wrote:
Christopher Schultz wrote:
...
I've even seen a site with a Perl-based (or was it PHP-based) service
..
must have been PHP, not Perl, I'm sure. We Perl guys don't do things
that way.
As I was telling Leo off-line, we have a nice global switch calle
Christopher Schultz wrote:
...
I've even seen a site with a Perl-based (or was it PHP-based) service
..
must have been PHP, not Perl, I'm sure. We Perl guys don't do things that way.
As I was telling Leo off-line, we have a nice global switch called "fatals_to_browser",
which you can just tu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 11/30/12 5:28 PM, Caldarale, Charles R wrote:
>> From: Leo Donahue - RDSA IT [mailto:leodona...@mail.maricopa.gov]
>> Subject: RE: Error page messages
>
>> I don't know of any public facing websites, off h
>-Original Message-
>From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
>Sent: Friday, November 30, 2012 3:28 PM
>To: Tomcat Users List
>Subject: RE: Error page messages
>
>> From: Leo Donahue - RDSA IT [mailto:leodona...@mail.maricopa.gov]
>> Su
>-Original Message-
>From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>Sent: Friday, November 30, 2012 3:19 PM
>To: Tomcat Users List
>Subject: Re: Error page messages
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Leo,
>
>On 11/
>-Original Message-
>From: Pid [mailto:p...@pidster.com]
>Sent: Friday, November 30, 2012 3:13 PM
>To: Tomcat Users List
>Subject: Re: Error page messages
>
>On 30/11/2012 22:09, Leo Donahue - RDSA IT wrote:
>>> -Original Message-
>>> From:
> From: Leo Donahue - RDSA IT [mailto:leodona...@mail.maricopa.gov]
> Subject: RE: Error page messages
> I don't know of any public facing websites, off hand, that show uncaught
> exception messages.
You need to get out more - there are tons of poorly implemented websites th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leo,
On 11/30/12 5:09 PM, Leo Donahue - RDSA IT wrote:
>> -Original Message- From: Pid [mailto:p...@pidster.com]
>> Sent: Friday, November 30, 2012 3:04 PM To: Tomcat Users List
>> Subject: Re: Error page messages
>>
On 30/11/2012 22:09, Leo Donahue - RDSA IT wrote:
>> -Original Message-
>> From: Pid [mailto:p...@pidster.com]
>> Sent: Friday, November 30, 2012 3:04 PM
>> To: Tomcat Users List
>> Subject: Re: Error page messages
>>
>> On 30/11/2012 21:00,
>-Original Message-
>From: Pid [mailto:p...@pidster.com]
>Sent: Friday, November 30, 2012 3:04 PM
>To: Tomcat Users List
>Subject: Re: Error page messages
>
>On 30/11/2012 21:00, Leo Donahue - RDSA IT wrote:
>> Are there standardized server responses that one
exception isn't handled* by the app then it's 500 and a stacktrace
if you haven't configured a custom error page. Those packages probably
have a few tens of exceptions that could be thrown.
> I don't know that I would expect to see any of these on a public website, as
> I am
Are there standardized server responses that one should expect to see when
dealing with java.lang, javax.servlet and javax.faces exceptions that should be
displayed to the client?
I don't know that I would expect to see any of these on a public website, as I
am likely not to care what happens o
x()).addMapping("/error.jspx");
On Wed, Oct 10, 2012 at 8:06 PM, Sean Owen wrote:
> Hello all,
>
> I'm looking for any ideas on the following issue:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=53958
>
> On Tomcat 7.0.32, using embedded Tomcat, I'm s
Hello all,
I'm looking for any ideas on the following issue:
https://issues.apache.org/bugzilla/show_bug.cgi?id=53958
On Tomcat 7.0.32, using embedded Tomcat, I'm seeing a
NullPointerException when using a custom error page. The page itself
is fine and loads if accessed directly. Tri
On Sat, 11 Aug 2012 09:07:11 +0100
Mark Thomas wrote:
>
> You are already in an error page so sendError will not trigger the
> error page matching process again. If it did there is a strong
> possibility that you could end up in an infinite loop.
>
> Mark
>
Thi
On 11/08/2012 08:17, Vladimir Mokrozub wrote:
>> On Fri, 10 Aug 2012 10:50:17 -0400
>> Christopher Schultz wrote:
>
>>>
>>> When I try to send error page directly from ErrorHandler using
>>> HttpServletResponse, it works fine and page is displayed, so
>On Fri, 10 Aug 2012 10:50:17 -0400
>Christopher Schultz wrote:
> >
> > When I try to send error page directly from ErrorHandler using
> > HttpServletResponse, it works fine and page is displayed, so it
> > seems the problem is with sendError() method. Is this an
; protected void doPost(HttpServletRequest request,
> HttpServletResponse response) throws ServletException, IOException
> { doGet(request, response); } } -
>
> When I type http:///TestServlet in the address bar, I
> get an empty page instead of default Tomcat error page,
Hello,
I have a problem (tried Tomcat 7.0.29 and Glassfish 3.1) with
displaying an error page when exception is thrown and processed by
another servlet.
Here is what I've added to web.xml:
-
java.lang.Throwable
/ErrorHandler
-
Here
-Ursprüngliche Nachricht-
Von:Mark Thomas
Gesendet: Mo 14.05.2012 18:25
Betreff:Re: AW: Manager activeSessions and customized error page
An: Tomcat Users List ;
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 14/05/2012 16:58, Christopher S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/05/2012 16:58, Christopher Schultz wrote:
> Thomas,
>
> On 5/14/12 9:44 AM, Thomas Rohde wrote:
>> A Filter was my first approach. But the filter is invoked after
>> authentication has taken place. And for authentication a session
>> is neede
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas,
On 5/14/12 9:44 AM, Thomas Rohde wrote:
> A Filter was my first approach. But the filter is invoked after
> authentication has taken place. And for authentication a session
> is needed. ;-)
Right: the form authenticator is in a Valve and Va
-Ursprüngliche Nachricht-
Von:Konstantin Kolinko
Gesendet: Mo 14.05.2012 15:00
Betreff:Re: Manager activeSessions and customized error page
An: Tomcat Users List ;
> 2012/5/14 Thomas Rohde :
> > Hi!
> >
> > I configured the Manager's maxA
ion we
> catch this exception around httpServletRequest.getSession(true) and redirect
> to an customized error page. Works!
>
> Now I activated form based authentication via securiy constraint in web.xml.
> If I try to open the web application with my browser by sending the first
&g
getSession(true) and redirect to an
customized error page. Works!
Now I activated form based authentication via securiy constraint in web.xml. If
I try to open the web application with my browser by sending the first request,
the response is empty (status 200 OK).
Is there any way to map a st
HttpServletResponse.sendError(). Once I
re-structured the code to not commit the response, it started working.
If I change the error-page entry to reference a static HTML page, the page
is displayed as expected.
This looks like a bug to me, but I wanted to run it past tomcat-user and
see what other people think.
1
code I have
if (someCondition) {
res.sendError(HttpServletResponse.SC_FORBIDDEN);
return;
}
When this code is hit, my custom page is not displayed. I get a
blank page.
No error is thrown by tomcat.
If I change the error-page entry to reference a static HTML page,
the page
is displayed
) {
res.sendError(HttpServletResponse.SC_FORBIDDEN);
return;
}
When this code is hit, my custom page is not displayed. I get a blank page.
No error is thrown by tomcat.
If I change the error-page entry to reference a static HTML page, the page
is displayed as expected.
This looks like a bug to
gt;
> if (someCondition) {
> res.sendError(HttpServletResponse.SC_FORBIDDEN);
> return;
> }
>
> When this code is hit, my custom page is not displayed. I get a blank page.
> No error is thrown by tomcat.
>
> If I change the error-page entry to reference a static HTML page,
code is hit, my custom page is not displayed. I get a blank
page. No error is thrown by tomcat.
If I change the error-page entry to reference a static HTML page, the
page is displayed as expected.
This looks like a bug to me, but I wanted to run it past tomcat-user
and see what other people
Hello,
in somecases, Tomcat dosn't allow output of an error page for too many active
sessions.
Reproduction:
1) Configure Tomcat 6 or 7 example application to allow maxActiveSessions=1
only (e.g. adding /examples/META-INF/context.xml#SimpeSessionManager...)
2) Visit http://localhost
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin,
On 6/7/2011 8:56 AM, Kevin Claver wrote:
> Through further investigation, I now believe the JSF framework I'm
> using is absorbing the error, and the framework's error page is what
> is throwing the 500 error. I wonder if t
Chris,
Through further investigation, I now believe the JSF framework I'm using is
absorbing the error, and the framework's error page is what is throwing the 500
error. I wonder if the 500 error thrown by the framework's error page should
fall through to the custom error pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin,
On 6/3/2011 9:43 AM, Kevin Claver wrote:
> When the custom error servlet fails to display, I get the stock tomcat http
> 500 error page.
>
> If I look at the access log, I see the 500 error:
>
> 192.168.xxx.xxx - - [02
Friday, June 3, 2011 7:47 AM
Subject: RE: error-page for http 500 error code does not work
> From: Kevin Claver [mailto:kcla...@yahoo.com]
> Subject: Re: error-page for http 500 error code does not work
> I zipped the tomcat install and deployed it to my Win 7 machine
> where it works
> From: Kevin Claver [mailto:kcla...@yahoo.com]
> Subject: Re: error-page for http 500 error code does not work
> I zipped the tomcat install and deployed it to my Win 7 machine
> where it works without issue.
I'll hazard a guess that you have a case sensitivity issue.
Thanks for the quick reply!
I zipped the tomcat install and deployed it to my Win 7 machine where it works
without issue.
When the custom error servlet fails to display, I get the stock tomcat http 500
error page.
If I look at the access log, I see the 500 error:
192.168.xxx.xxx - - [02/Jun
On 02/06/2011 21:45, Kevin Claver wrote:
> Two things I would like to note:
>
> 1. When I invoke the Java HMAExceptionHandlerServlet configured to be used
> in the error-page block in the application specific web.xml directly from the
> URL in the browser, it works.
>
> 2
ut never a solution.
My Tomcat version:
Apache Tomcat 5.5.33 (I've also tried 5.5.27 and 6.0.32)
running on:
Fedora 2.6.27.5-117.fc10.x86_64
Two things I would like to note:
1. When I invoke the Java HMAExceptionHandlerServlet configured to be used in
the error-page block in the appli
1 - 100 of 382 matches
Mail list logo
