When I browse directly to it I have no problem viewing it, however if I try to get there via the reverse proxy I get a blank page. Wireshark shows me a 503, but this one is coming from the Apache reverse proxy (IP 100.100.100.100) and not the Tomcat (IP 1.1.1.1).

Should I add http://1.1.1.1/AppName/ to the config? How? I tried it but I get a blank page, however this one shows on the URL bar of the browser the internal IP of the Tomcat, so, no go.

When you browse to 100.100.100.100/AppName/summary,html it presents a blank page and the URL on the browser gets changed to 1.1.1.1/AppName/summary.html.
–
Mr AlephJan 30 '12 at 15:43

Also, what if I want to do a generic error handling on Tomcat. Ideally every time a 404 or 500 or whatever is thrown I want to show a customized error.html. I have that in place on the config for Tomcat, however with the VirtualHost on Apache it doesn't display the error page either.
–
Mr AlephJan 30 '12 at 15:46

@MrAleph Then you need to trace what's actually happening with the request; something's responding with a redirect, but Apache shouldn't allow that Location header in a response unmodified with a proper ProxyPassReverse config in place. Have you tried with the configs that I've provided?
–
Shane Madden♦Jan 30 '12 at 16:10

I am doing it as I type. I'll post the reply in a bit. Thanks for the help
–
Mr AlephJan 30 '12 at 16:13

Same story. All I get is a blank page. If I go directly to 1.1.1.1 then it's fine. Just as a test I assigned an external IP to 1.1.1.1. If I go directly to that one as 300.300.300.300/AppName/symmary.html then it's also fine. The minute I try from the reverse proxy then it doesn't work. So my guess is that the reverse proxy doesn't know where to go get that file. I can hardcode it as you said as ProxyPass /AppName/summary.html http://1.1.1.1/AppName/summary.html but that would not work for the error pages or if I want to add more pages
–
Mr AlephJan 30 '12 at 18:25