mod_jk errors with tomcat 6.0.20 and Apache 2.0.52

2010-01-22 Thread Matt Turner
Hi All, I have an existing Apache 2.0.52 installation, and a new tomcat 6.0.20 installation. They are both sitting on the same Linux box - uname -a returns the following: Linux [machine name] 2.6.9-55.ELsmp #1 SMP Fri Apr 20 16:36:54 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux I'd like if

RE: mod_jk errors with tomcat 6.0.20 and Apache 2.0.52

2010-01-22 Thread Matt Turner
or not the data arrived securely or not at httpd. I suspect you'll get a better answer once the States wakes up, but that's my guess. - Peter 2010/1/22 Matt Turner m4tt_tur...@hotmail.com: Hi All, I have an existing Apache 2.0.52 installation, and a new tomcat 6.0.20

RE: mod_jk errors with tomcat 6.0.20 and Apache 2.0.52

2010-01-22 Thread Matt Turner
In my case sometimes I do need to pass through the SSL to Tomcat, as I'm running CAS which requires geniune SSL requests. (I do also have some SSL requests that tomcat doesn't need to see - which I will send via 8009 as has been suggested). The SSL pass-through requirement explains why I

RE: mod_jk errors with tomcat 6.0.20 and Apache 2.0.52

2010-01-22 Thread Matt Turner
From: ch...@christopherschultz.net To: users@tomcat.apache.org Subject: Re: mod_jk errors with tomcat 6.0.20 and Apache 2.0.52 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matt, On 1/22/2010 9:25 AM, Matt Turner wrote: In my case sometimes I do need to pass through the SSL to Tomcat