There are a few things why we use apache with mod_jk. First of all it
would not be possible to run Tomcat as user because it should listen on
port 80/443. Additionally we can use mod_security to precheck requests
delivered to tomcat to remove use- and sensless requests and minimise
the risk of attacks.
The second thing is that apache is faster with delivering static files
(maybe we will use Tux as well).
Third thing is if something happens to tomcat we are still able to
display a please-come-back-later-site with apache.
If some things mentioned above are not correct I would appreciate to
here about it, of course with useful arguments.
Markus
Am 16.05.2010 18:44, schrieb Caldarale, Charles R:
From: Markus Mehrwald [mailto:mmehrw...@gmx.at]
Subject: Re: mod_jk file not found
I did not find the actual problem but I can live with this script not
delivered by apache. Maybe this is because the js is inside a jar file?
Since you don't seem to be using httpd for anything useful, why not just
eliminate it, and serve everything with Tomcat? If you enable the APR
connector, Tomcat will even handle SSL just as fast as httpd, and you use the
same SSL setup that you had with httpd.
http://tomcat.apache.org/tomcat-6.0-doc/apr.html
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
