Eric

Thanks for the reply. I tried this:

NameVirtualHost *:443

<VirtualHost *:443>
        ServerAdmin webmas...@localhost

        SSLEngine On
        SSLCertificateFile /etc/apache2/ssl/apache.pem

#=======

ProxyPass /SFXServer/ balancer://backtcserver/


and it seem to work. Issue I now hit is I get a 404 from my backend Tomcat

"203.217.63.195 - - [18/Aug/2010:13:47:14 +0000] "POST 
/SFXServer/spring/messagebroker/amf HTTP/1.1" 404 522 "-" "Mozilla/5.0 
(Macintosh; U; Intel Mac OS X 10_6_4; en-US) AppleWebKit/533.4 (KHTML, like 
Gecko) Chrome/5.0.375.126 Safari/533.4"
"

Is there a way to enable more detailed debugging to see why? If I have the 
proxy pass in httpd.conf, I do not get this error, but I can reach the backend 
Tomcat on the same URL using http and https, which is not what I want.


Thanks
Des




On 18/08/2010, at 11:51 PM, Eric Covener wrote:

> On Wed, Aug 18, 2010 at 8:22 AM, Des Hartman <[email protected]> wrote:
>> Hi,
>> 
>> Is there a simple way to do the following:
>> 
>> 1) All "http" based requests to website www.abc.com go to my Apache2 server 
>> regardless of the virtual site
>> 
>> 2) All "https" based requests to website www.abc.com are proxied to a 
>> private tomcat server via mod_proxy
> 
> You already need two vhosts for the two frontend protocols. Just put
> ProxyPass directives in the SSL vhost.
> 
> -- 
> Eric Covener
> [email protected]
> 
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: [email protected]
>   "   from the digest: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
   "   from the digest: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to