-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt,
On 1/22/2010 5:09 PM, Matt Turner wrote:
> In between times I tried the ProxyPass which seems to work fine, but I'd much
> rather use plain AJP so I'll try that next.
AJP is the protocol used by both mod_jk and mod_proxy_ajp (which is what
you
010 14:53:21 -0500
> 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:
> >
-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, as
> I'm running CAS which requires geniune SSL requests.
mod_jk ought to be able to forward all SSL information to Tomcat.
Specificall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 1/22/2010 7:49 AM, Peter Crowther wrote:
> - You're telling AJP to use a secure connection between httpd and Tomcat;
AJP doesn't recognize any "secure" connection capability for its own
communication. As you've said, AJP /does/ forward SSL
Am Fri, 22 Jan 2010 14:25:11 +
schrieb Matt Turner :
> The SSL pass-through requirement explains why I was attempting to
> pass through to :8443 directly - but it sounds like that's the wrong
> approach.
If it isn't possible to move the SSL-certificate and -keys to the
Apache2 (and change the
ataneo.eu
> To: users@tomcat.apache.org
> Subject: Re: mod_jk errors with tomcat 6.0.20 and Apache 2.0.52
>
> I guess that you should exchange the "JkMount /* tomcatssl" by
> "JkMount /* tomcat1" provided you use a "standard" Tomcat-setup.
>
> For a parallel
I guess that you should exchange the "JkMount /* tomcatssl" by
"JkMount /* tomcat1" provided you use a "standard" Tomcat-setup.
For a parallel SSL- + Non-SSL-Setup using Apache2 you basically need 2
virtual-hosts in Apache2. One for Port 443 with the
standard-SSL-parameters Apache2 expects to inte
OK - sounds likely, many thanks.
I'll give that a whirl.
> Date: Fri, 22 Jan 2010 12:49:49 +
> Subject: Re: mod_jk errors with tomcat 6.0.20 and Apache 2.0.52
> From: peter.crowt...@melandra.com
> To: users@tomcat.apache.org
>
> I'm not an AJP expert, but I su
I'm not an AJP expert, but I suspect:
- You're telling AJP to use a secure connection between httpd and Tomcat;
- The Tomcat connector on port 8443 is a SSL connector, not an AJP connector;
- AJP is getting confused.
I believe you should only need to configure one worker (the one on
8009); AJP is
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
10 matches
Mail list logo
