SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 3/17/15 11:12 AM, Rainer Jung wrote:
Am 17.03.2015 um 15:40 schrieb Sascha Skorupa:
Hi Rainer,
currently not (Apache 2.2) but it might be an option to upgrade
the OS and the Apache if it leads to a solution.
OK. But think twice, whether it is better
, Sascha Skorupa wrote:
Hi,
here:
http://grokbase.com/t/tomcat/users/13bvsbwb8s/multiple-servers-and-
digest-authentication
the same problem is described and the recommended solution is to use
sticky load balancing. But, the problem in a tomcat cluster is that
the session ID
: Re: Migration from Tomcat6-Cluster to Tomcat7-Cluster: Digest
Authentication problem
Hi Sascha,
Am 17.03.2015 um 13:02 schrieb Sascha Skorupa:
Rainer, thank you for this hint, but unfortunately, this feature is too new
to be included in any current mod_jk linux package and building it from
authentication. The first http response (401 with
Authentication Header) does not contain a session ID.
How should sticky load balancing be configured or how to enforce session id
generation before authentication?
Regards
Olschi
Von: Sascha Skorupa
Gesendet: Mittwoch, 4. März 2015 16:21
An: 'users
Hi,
because of changes in the HTTP digest implementation within the JDK 8
(https://bugs.openjdk.java.net/browse/JDK-8010505), we are forced to migrate
from tomcat 6 to 7.
The problem is that we have a tomcat cluster (several tomcats behind an
apache/modjk server) and we cannot guarantee that