Thanks. Squid may be a contender but I need the CMS and blogging that comes with apache/php. Although maybe someday our traffic may get to the point where we will need squid to keep up! Now that would be a good problem to have! Thanks for the pointer.
On Mon, 16 Nov 2009 15:36 -0800, "Elli Albek" <e...@sustainlane.com> wrote: > You can also look at squid to serve static files and load balance. So > squid fronts tomcat and your other apps. Squid can serve your static > files as well. All you have to do it make sure your static files > return a cache header like max-age, and squid will serve them without > going to the origin (tomcat). Squid can also load balance tomcats and > route requests for multiple origins based on some rules. We have squid > doing virtual hosting of tomcats that run different apps, as well as > serving static content and caching dynamic content. > > The down sides vs apache: > 1. Not as many plugins and options > 2. The configuration rules are simpler and more widely > known/understood in apache > 3. Hard to rewrite URLs. Not impossible, but mod rewrite is much much > easier to deal with. Actually any manipulation of the request/response > is less than trivial on squid. > > If you go for squid, 2.7 and above. Earlier versions are not as good > for reverse proxing. > > --------------------------------------------------------------------- > 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
