Hi Chris - Sorry for the "HELP NEEDED". What actually happens is that, just for https://my.webserver.com/, I get served the pages that are at the apache root, *not* what is being served by tomcat at port 8443.
I do get the tomcat pages if I explicitly add the port, i.e. https://my.webserver.com:8443/ So, the reverse proxy seems to be broken for https only. The reverse proxy works fine for http, i.e. http://my.webserver.com/ gets the tomcat pages served at http://my.webserver.com:8080/ Jeff Christopher Schultz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Jeff, > > On 3/3/14, 5:11 PM, Jeff Haferman wrote: >> Yes, for development httpd and tomcat are on the same physical >> machine. Eventually they will be on different machines. But, even >> if I try browser <--- HTTPS --> httpd <-- HTTP --> Tomcat by just >> changing the ProxyPass and ProxyPassReverse directives to use the >> unencrypted URLs as follows >> >> <VirtualHost *:443> SSLEngine on SSLProxyEngine on >> SSLCertificateFile /path/to/server.crt SSLCertificateKeyFile >> /path/to/server.key ServerName my.webserver.com ProxyPass / >> http://my.webserver.com:8080/ ProxyPassReverse / >> http://my.webserver.com:8080/ </VirtualHost> >> >> the reverse proxy still does not serve the tomcat pages as I would >> expect. > > Given the above setup, what /actually/ happens when you try to request > a resource that should go to Tomcat? "does not serve pages as I > expect" is not a good description. > > Oh, and everyone posting NEEDS HELP to it's not necessary to add "HELP > NEEDED" or similar text to your subjects. > > - -chris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
