Dave Hall <dave.hall@skwashd.com> writes:
Depending on what is running on the backend service you might find it better for performance to use Varnish (a web accelerator) to proxy the requests. Varnish will serve you static assets (images/css/js etc) from RAM and depending on the backend app config it could do the same for pages too.
+1. I looked at varnish and nginx; IIRC the main reason I'm using apache on epoxy.cyber.com.au is because it was easy to have it do the auth layer, and auth against a slapd RFC2307 ppolicy-overlay backend. My main concern with varnish was needing to install cc to configure it, because more packages = more bad. If I'd gone with varnish, I probably would have set up a little script to configure it on the buildhost and scp it over.