Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I would like to build a webserver instance in Amazon that handles both PHP and static requests. Here's my idea ... is it crazy to join varnish + apache + lighttpd ?

Varnish in port 80 handling as reverse proxy. Apache2 in port 8080 to server PHP files (main requests to web pages) (called by Varnish) Lighttpd in port 81 to server just static files (called by HTML files)

The domains use to main web page ( and static content ( will pass through the Amazon ELB.

Make all sense ?

share|improve this question

no point to use lighttpd.

If you use varnish the static content can be set to be cached and served with varnish. It'll be a lot quicker then lighttpd also.

But yes.. you can do that setup

share|improve this answer
will varnish handle static content as good as lighttpd does ? i didn't know that about varnish ... i usually use lighttpd or nginx for static content – user75317 Jul 9 '11 at 0:39
so, do you think it will be better without the lighttpd (webserver just for static content) ? – user75317 Jul 9 '11 at 2:38
varnish will destroy lighttpd serving static content that is in the varnish cache. – Mike Jul 9 '11 at 4:55
ok, thank you ! – user75317 Jul 9 '11 at 14:34

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.