Hi Andre,
Did you look at what is in the mod_jk.log file ?
Yes. Following is mod_jk log:
[Thu Jan 08 09:18:24 2015] [4800:4424] [info] init_jk::mod_jk.c (3383):
mod_jk/1.2.40 initialized
[Thu Jan 08 09:18:25 2015] [4800:4424] [info] init_jk::mod_jk.c (3383):
mod_jk/1.2.40 initialized
[Thu Jan 08
Sandip Gaikwad wrote:
Hi Rainer,
In addition to the comments form André: JkMount is by default only active
in the vhost in which you configure it. If your Apache config contains some
VirtualHost which matches your request but doesn't contain the JkMount in
its ocnfig, then the rule will not
Hi Rainer,
In addition to the comments form André: JkMount is by default only active
in the vhost in which you configure it. If your Apache config contains some
VirtualHost which matches your request but doesn't contain the JkMount in
its ocnfig, then the rule will not trigger.
You can add
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
On 1/8/15 6:21 PM, Caldarale, Charles R wrote:
From: dmccrthy [mailto:dmccr...@gmail.com] Subject: Re: Tomcat
7.0.56 - How to configure Tomcat/JRE 7u72 for client HTTPS Mutual
Authentication connections
I found
Source of question:
http://stackoverflow.com/questions/27868936/java-lang-classnotfoundexception-javax-ws-rs-messageprocessingexception
I am deploying a war to Tomcat 7.0.57. This code uses Jersey 2.x Client to
communicate with a Rest endpoint and exposes its own Rest endpoints using
CXF (AKA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 1/8/15 5:07 PM, André Warnier wrote:
dmccrthy wrote:
Chris, André,
Many thanks. I hadn't considered either the MITM or Apache HTTPD
angles. The proxy idea occurred to me (sorry, I had a typo in my
original mail and that may not
Hello,
With debugging I finally found out why Jersey and Tomcat doesn't play well with
digest authentication.
If a nonce got stale and tomcat issues a new authentication request. Jersey
answers this request and responds with a valid header in terms of the HTTP
digest specification.
The
On 09/01/2015 13:36, Kehlenbach, Andreas wrote:
Hello,
With debugging I finally found out why Jersey and Tomcat doesn't play
well with digest authentication.
If a nonce got stale and tomcat issues a new authentication request.
Jersey answers this request and responds with a valid header
Hello Chris,
Currently I've attached tomcat sources to my sample application.
The following I found out:
1) The problem occurs only if the nonce timed out.
1.1) After the nonce timed out, tomcat sends a new nonce, which the client
correctly respond to. The new response contains the last send
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
On 1/8/15 6:21 PM, Caldarale, Charles R wrote:
From: dmccrthy [mailto:dmccr...@gmail.com] Subject: Re: Tomcat
7.0.56 - How to configure Tomcat/JRE 7u72 for client HTTPS Mutual
Authentication connections
I found the link below from
10 matches
Mail list logo
