In case you prefer the gospel according to the erudite Mr Eggers... On 21/12/2011 15:24, Mark Eggers wrote: > Well, you sort of kind of followed that. > > Now, as Pid has also pointed out, you will need to configure mod_proxy, > mod_proxy_ajp, or mod_ajp to connect Apache HTTPD and Tomcat. > > There is a lot of information about how to configure mod_proxy_ajp on the > list, as well as a nice sample configuration file in recent source releases > of the Tomcat connectors (see the following download page - > http://tomcat.apache.org/download-connectors.cgi). Once you unpack the > download, an example can be found in the conf directory. > > There are a couple of reasons to run Apache HTTPD <--> AJP <---> Tomcat. For > example; if you don't want to run Tomcat on port 80, if you serve other > content (like PHP), or if you have Apache HTTPD modules that provide > functionality that Tomcat does not (some authentication modules). If you > don't have these types of requirements, then it's much easier to run Tomcat > by itself on port 80 and be done with it.
As above, you will need to configure mod_jk or mod_proxy and mod_proxy_ajp or mod_proxy_http. p -- [key:62590808]
signature.asc
Description: OpenPGP digital signature
