-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cyrille,
On 2/26/2010 4:22 AM, Cyrille Le Clerc wrote:
> I meant x-forwarded-proto rather than x-forwarded-for.
>
> Here is a sample of configuration where Apache adds the header
> X-Forwarded-Proto and Tomcat RemoteIpValve handles it.
I think the O
. When I redirect to the
> > TomCat servlet I get a 404. If I switch to http everything works fine.
> > Shouldn't I be able to use https/443on my web server and http/8080 on the
> > app server without issue? How?
> > --
> > View this message in context:
> > http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it may concern,
On 2/25/2010 10:56 AM, sikorsky wrote:
> I'm new to Apache 2.2 and TomCat 6.0. I thought I could use SSL on
> my Apache web server and not need to have SSL on my Tomcat
> applications.
You can.
> Especially since they are
On 25/02/2010 15:56, sikorsky wrote:
I'm new to Apache 2.2 and TomCat 6.0. I thought I could use SSL on my Apache
web server and not need to have SSL on my TomCat applications. Especially
since they are both on the same server. I installed an Entrust Cert on my
Apache webserver and it works f
> --
> View this message in context:
> http://old.nabble.com/Apache-2.2-and-TomCat-6.0-using-SSL-tp27714427p27714427.html
> Sent from the Tomcat - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-ma
ct to the
TomCat servlet I get a 404. If I switch to http everything works fine.
Shouldn't I be able to use https/443on my web server and http/8080 on the
app server without issue? How?
--
View this message in context:
http://old.nabble.com/Apache-2.2-and-TomCat-6.0-using-SSL-tp27714427p277
