Configuring Apache httpd as a reverse proxy for Apache Tomcat is a task with many options and lots of hidden pitfalls. This session will cover the options, the pitfalls and explain how to avoid them.
One is almost spoilt for choice when configuring Apache httpd as a reverse proxy to one or more Apache Tomcat instances. With three httpd modules, two protocols and three Tomcat Connector implementations for each protocol it is not always clear which combination is right for a given situation.
The first part of this session will examine each of the options and provide guidance as to the factors to consider when selecting an approach to implement a reverse proxy. The second part of the session will examine the things that can go wrong, explain how to identify the problem and what steps to take to fix it.
Outline: - Introduction: Who am I? - Background: Brief overview of reverse proxying - httpd module selection: mod_jk vs mod_proxy - protocol selection: HTTP vs. AJP - connector selection: BIO vs. NIO vs. APR - load-balancing vs. clustering - lost session problems - broken link problems - virtual host selection problems - SSL problems - security problems - other potential problem areas - questions