-connector and tried the same - and there the
SSL Session ID worked properly and wasn't lost preemptively.
Does someone know something about problems with SSL Session IDs with
Apache und mod_jk? Does someone have a solution how
to remove that problem?
Thank you in advance,
Oliver Schoenwald
Hello,
how do I track sessions without using cookies or URL-writing?
Following the Servlet API 2.3, the third way to track sessions is by
using the SSL-Layer to hold the ID.
I have tried that out with my installation (Apache 2.0.47, mod_jk2,
Tomcat 5.5.4) and followed the
configuration hints
Hello,
why does the use of references like ${user.home} not work while the
reference ${catalina.home} and ${catalina.base} is usable in the
.catalina.properties-file?
Greetings,
Oliver Schoenwald
-
To unsubscribe, e-mail
the problem more properly or
even know how to solve it (without changing some of the components like
using another servlet container engine or another JVM).
Thank you for any help,
Oliver Schoenwald
University of Hagen
Germany
Oliver Schoenwald wrote:
Our system configuration is as follows:
SUN Fire
to hear of it.
Thank you in advance,
Oliver Schoenwald
FernUniversitaet Hagen
Germany
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Oliver Schoenwald [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 4:18 AM
To: Tomcat Users List
Subject: Configuring Tomcat 4.1.18 to handle 401 http errors
Good morning!
some days ago I already asked
Good morning!
some days ago I already asked a question regarding this context, but I
had some time to
dive a bit into the Servlet API 2.3 Specification. So far, it seems that
the specification states
that the container, not the servlet, is the layer attached to the
client. And the container,
Hello,
we have updated from Tomcat 3.2.4 to 4.1.8 and now have problems with
one of our servlets.
Under 3.2.4, this servlet send an HTTP_UNAUTHORIZED under certain
circumstances and the
Browser popped up his Login-Windows. Now, under 4.1.8, the engine
catches this error and
wraps an html-page
