Rainer Jung rainer.jung at kippdata.de writes:
On 09.03.2009 18:07, Anthony J. Biacco wrote:
Download the latest, configure, make, make install, check for
new/deprecated directives in the jk docs, modify configs accordingly,
reload apache.
I'm running apache 2.2.9, mod_jk 1.2.27 and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 3/20/2009 8:02 AM, André Cruz wrote:
I'm running apache 2.2.9, mod_jk 1.2.27 and tomcat 6.0.18 and I get this
problem
as well:
GET /shibboleth-idp/SSO HTTP/1.1
[snip]
HTTP/1.1 302 Moved Temporarily
Date: Fri, 20 Mar 2009 11:11:24
: Sunday, March 8, 2009 1:04:59 PM
Subject: Re: mod_jk and 304
On 07.03.2009 22:22, Anthony J. Biacco wrote:
If you have your jkloglevel set to at least info, the modjk log file
(whatever you have it set to) will show the jk version when apache is
started or reloaded
Old versions unfortunately did
://www.formatdynamics.com
-Original Message-
From: Eqbal [mailto:eqb...@yahoo.com]
Sent: Monday, March 09, 2009 10:07 AM
To: Tomcat Users List
Subject: Re: mod_jk and 304
Thanks for the tip Rainer. The version I have is 1.2.6-dev
So in order to update to a newer version, do I just download the latest
and copy
On 09.03.2009 18:07, Anthony J. Biacco wrote:
Download the latest, configure, make, make install, check for
new/deprecated directives in the jk docs, modify configs accordingly,
reload apache.
+1
Rainer
-
To unsubscribe,
I have tomcat running behind apache http server 2.0 using mod_jk. I have
noticed that this causes any response to request for files in tomcat that
return a 304 status code, to also have a 20 byte message body attached to the
response. This causes our load balancer to think this is an error as
