Putting apache in front also allowed me to serve static docs, SSL, and proxy all in one place, with mod_perl off by itself in the back end. I like the separation of concerns, and my config files are so much simpler! (Thanks go to the practical mod_perl book for the full inspiration.) Serving images w/ KeepAlive on over light httpd children in front is SO much faster than serving it all with big, intertially-challenged mod_perl children. My entire pages load much, much faster now.
Cheers,
Nathan
Larry Leszczynski wrote:
On Tue, 3 Aug 2004, Philippe M. Chiasson wrote:
I've had lots of success with a light reverse proxy (httpd or squid) in front of my mod_perl servers. I would recommend it, as it's simpler than 2 completely separate servers for dynamic content and static stuff.
I like squid for this, as it's virtually drop-in and play.
I also prefer a reverse proxy to separate servers, but I generally prefer httpd to squid mainly because I really like having mod_rewrite available, just in case - it's really handy in a pinch and has gotten me out of a lot of jams when unexpected situations arise...
Larry
--
Nathan L. Kugland [EMAIL PROTECTED]
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
