Hi, There are at least 3 different approaches for configuring Apache httpd 2.2 to act as a reverse proxy for Tomcat 7.0:
a) mod_proxy_http b) mod_proxy_ajp c) mod_jk There's been quite a lot of discussion about the differences of each one but a lot of that discussion appears to be either not very analytical or outdated. What are the current differences and tradeoffs with using these alternatives? Quite a few writers appear recommend mod_jk if performance and HA features are critical. But Apache 2.2 mod_proxy supports some load balancing and failover features through mod_proxy_balancer. Also, mod_cache can be used to offload static resource serving from the back-end to provide something similar to JkMount. Does mod_jk still have a lead when it comes to these features? >From a setup point of view, using mod_proxy_http/ajp is a lot simpler than mod_jk because e.g. on a Linux system you can typically install these using a system package manager. For mod_jk you need to either have a compilation environment on your production system (which the sysops don't like) or compile and package the module on another machine with a compatible OS setup. marko