I have the same issues. Everything worked fine with Tomcat 4.1 but since Tomcat
7.0 not. I checked all below.
Nothing, yet when you look at Tomcat's listening connection log file, there is
communication with Tomcat, but no page is displayed.
Philip Coetzee -Technical Manager, Southern African
Guys,
if you want help, you are going to have to make an effort and be a bit systematic in your
answers. Phrases like it does'nt work and there is communication with Tomcat don't
help, because they don't really mean anything to someone trying to help you.
So could you, for example, go
Hi everyone,
I'm actually using Tomcat on my environment platform (Tomcat 5.5 / Tomcat 6
and soon Tomcat 7). I have a frontend Apache http Server using the jk
connector to communicate with Tomcat instance.
I'd like to change this connector and use the mod_proxy one for several
reasons. The main
Sylvain Goulmy wrote:
Hi everyone,
I'm actually using Tomcat on my environment platform (Tomcat 5.5 / Tomcat 6
and soon Tomcat 7). I have a frontend Apache http Server using the jk
connector to communicate with Tomcat instance.
I'd like to change this connector and use the mod_proxy one for
Hello:
Ive got a web application running on Tomcat 7, with SSL (https) and
realm for authentication/authorization
When I invalidate() a session ( session.invalidate() ) , Tomcat
doesn't know it and thinks that user is still logged in
So, that user can get protected pages. Tomcat should return
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chema,
On 9/16/2011 7:37 AM, Chema wrote:
Ive got a web application running on Tomcat 7, with SSL (https)
and realm for authentication/authorization
Presumably, you are using CLIENT-CERT as your auth-method?
When I invalidate() a session (
Presumably, you are using CLIENT-CERT as your auth-method?
Not , FORM method
When I invalidate() a session ( session.invalidate() ) , Tomcat
doesn't know it and thinks that user is still logged in So, that
user can get protected pages. Tomcat should return him a login
window but doesn't.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shanti,
On 9/15/2011 4:21 AM, Yajnik, Shanti wrote:
Does anyone know when the fix for the specific vulnerability:
CVE-2011-3190 will be available for the 6.0.33 version of Apache
Tomcat?
The Tomcat team does not release binary patches, so there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 9/15/2011 3:17 AM, Mark Thomas wrote:
On 14/09/2011 23:03, Christopher Schultz wrote:
John,
On 9/13/2011 5:51 AM, John Bass wrote:
In the event of a node failure, I'm assuming that there's no
way to recover from that and the failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chema,
On 9/16/2011 1:25 PM, Chema wrote:
Presumably, you are using CLIENT-CERT as your auth-method?
No, [I am using] FORM method
Hmm. HttpSession.invalidate() *is* the proper way to terminate a
FORM authentication login.
Chris,
Christopher Schultz wrote:
...
Why do you think that HttpSession.invalidate() should act as a log out
mechanism when using CLIENT-CERT authentication?
I guess that where the OP (and I) get a little confused is in the distinction between the
state of having a session and being
I am TRing 5.5.34 today...
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Here goes web.xml and servlet.xml
I will note that server.xml contains SingleSignOn because I've got two
applications which share logging
?xml version=1.0 encoding=UTF-8?
web-app
!-- Authentication --
servlet
servlet-nameLoginServlet/servlet-name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 9/16/2011 1:38 PM, André Warnier wrote:
I guess that where the OP (and I) get a little confused is in the
distinction between the state of having a session and being
logged-in, and maybe the sequence in which these things happen.
1)
Version of Tomcat: Apache Tomcat 7.0
Server: Windows 2003
Problem: Configuring Tomcat 7.0 SSL using Apr Implementation
Apache Tomcat splash screen (https://localhost:8443https://localhost:8443/)
fails after including key, cert in server.xml configuration using following
entries:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 9/15/2011 1:02 PM, verlag.preis...@t-online.de wrote:
I would like to add that the Exceptions seems to have occured when
the client aborted the connection, because at the same time of the
exception, in the ISAPI log was the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 9/13/2011 1:21 PM, Jeffrey Janner wrote:
Our app currently is not distributable as a war file due to some
decisions made long ago (properties files that need to be modified
stored in WEB-INF, etc.).
[snip]
However, there is one
17 matches
Mail list logo