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'm bringing up my first production-level(-ish) server and have installed and configured a couple of python web applications, which I have to access like so:


The port is not so important, I can choose it of course. My question is if I should use Apache, DNSs, Apache+DNSs (and to what degree), or something completely different to move from that url scheme to a friendlier one:

share|improve this question
For HTTP port must be 80 if you don't want it included in the URL, and 443 for HTTPS. – Zoredache Dec 28 '12 at 19:47
Apache reverse-proxy or redirect directives can do what he's asking for though – mfinni Dec 28 '12 at 19:53
up vote 2 down vote accepted

You'll have to configure either a reverse-proxy or a redirect directive in Apache; you don't specify port numbers with DNS.

share|improve this answer
This looks like a sensible guide I'll check:… – dukeofgaming Dec 29 '12 at 22:21

Easy way : Keep the existing configuration same. Try rewriting the URL using mod_rewrite

Hard way: If you have access to DNS, you could have a seperate sub domains for different applications e.g. ,

share|improve this answer
That works too. – mfinni Dec 28 '12 at 20:09

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.