Greetings,
Does anyone know why Tomcat does not store the POST parameters when
launching j_security_check?
I suppose it is because the 2.2 spec says:
The URL path which triggered the authentication is stored by the
container.
Just the URL? Where are the POST data gone? (GET works ok, of
Greetings,
does anyone please know why Tomcat (3.2) takes 20 seconds to create a
session? ( God, this LONG time makes the connection pooling absurd! )
Thx in advance
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Hi again,
I'm in a Debian Linux 2.2 with Blackdown JDK1.3, in a PII-333. Anyway, i'll
try 3.2.1. Can you guys please tell me your times? I'll apreciate it in
order to choose the server the app will be later on.
Thx
-
To
Then, is it possible to initialize SecureRandom at startup time? You know,
the only thing I'm asking for is not to have the first client waiting 20
seconds to have his/her page loaded :-)
Alfredo
-
To unsubscribe, e-mail:
Hi again, just a couple of things about this little headache of mine :-) :
1. -It seems that SecureRandom initializes at startup time since Tomcat
3.2.2 (currently beta :- ( )
2.- So. what about that load-on-startup tag?? What are the possible
values it may have?
Thanks for the replies
Greetings,
I'm trying to use SSL with Tomcat 3.2. I've followed the SSL-Howto
guidelines and tomcat.log shows :
PoolTcpConnector : Starting HttpConnectionHandler on 8443
which I think s ok, but,
How do I know SSL is working?
I've tried to use the Request.getAuth() from a login servlet