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

should I run nginx for static content on port 81 or set it up as reverse proxy to apache?

Which is a better idea and why? I'm currently simply running nginx on port 81. i was wondering if there are any benefits as running it on port 80 instead and proxy to apache that sits on 8080 for example?

share|improve this question
up vote 2 down vote accepted

If you have clients in the corporate world than having a site that servers content on non-standard ports may cause issues. A lot of companies will only allow certain ports (80,443, sometimes 8080) out. This obviously isn't a universal standard but having someone email you saying your page loads but has no images or css can be a bit frustrating.

share|improve this answer

I find it a hassle to use a non standard port to handle HTTP. The devs have to make sure to always add the port option and secondly tomorrow if you decide to use a CDN you wouldn't be able to.

The other option could be that you configure another subdomain like and don't proxy it.

share|improve this answer
What Pratik Amin said is also true. – Sameer May 28 '11 at 1:50

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.