On Wed, Apr 14, 2010 at 3:15 PM, Brad Van Sickle <bvs7...@gmail.com> wrote: > So it sounds like Apache is simply not going to meet my needs. In the event > that I do need to replace Apache, hopefully you can save me some research > time and recommend me one of the listed options that fulfills my needs (or > confirm that perlbal does)
You may want to try Apache with the event mpm using mod_proxy. I haven't used that, I ended up using Perlbal mostly so I could customize the code without having to deal with intermittent segfaults like I did when I patched apache and got something wrong. > I need the following features: > 1) provides support for named virtual hosts > 2) supports SSL to the client > 3) supports URL rewriting (similar to mod_rewrite) > 4) knows the availability of pool members and provides high availability. > 5) the ability to serve static content itself I think perlbal does all of this. Getting it configured to do all of this may not be straightforward, but the perlbal list is very helpful for that. That being said, I've heard really great things about Varnish, so I'd try that if I didn't have perlbal. > I guess 5 isn't strictly neccessary, but it would be nice to serve static > content (css/js/images/etc...) from the same piece of technology without > proxying those requests to another Apache instance running on the same host > (or something) > > Thanks for all the help! > > On 4/14/2010 5:48 PM, Perrin Harkins wrote: >> >> On Wed, Apr 14, 2010 at 5:33 PM, Brad Van Sickle<bvs7...@gmail.com> >> wrote: >> >>> >>> I didn't find much info on perlbal after a quick glance, I'll certainly >>> give >>> it a closer look, but my inital reaction is that I'm leary of replacing >>> Apache on my web layer. I'm doing a few things with a few other modules ( >>> mod_rewrite for example) in addition to mod_proxy, and from what I was >>> able >>> to find in my initial look, I didn't see any support for some of those >>> types >>> of things. >>> >> >> There are many full-featured proxy servers these days. There's even >> mod_proxy_balancer for apache, but that doesn't do high-availability, >> which you're looking for. >> >> Check out some of these for reverse-proxying if you don't like perlbal: >> - nginx >> - lighttpd >> - varnish >> - pound >> >> All of those can serve as mod_perl frontends. >> >> - Perrin >> >
