Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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 have some subdomains I want to redirect to specific ports on the same server. Say I have 

I want to transparently redirect to and I want to preserve the original sub-domain name the url of the browser.

How do I do this with Apache 2.2? I have Apache 2.2 running on default port 80. I can't figure out the write configuration to get this to happen.

I have already set up to resolve in DNS to

This is for an intranet development server that has a non-routable ip address so I am not so concerned about exploits and security that would compromise a publicly facing server.

share|improve this question
do you want to see your client that it is being redirected or do you want it to seem as if everything is running on port 80? – Marcel G Oct 28 '10 at 15:17
everything on port 80 – Jarrod Roberson Feb 17 '11 at 22:33
up vote 36 down vote accepted


Here is what I finally came up with after being set in the right direction by Miles Erickson. I wanted the address bar to reflect the original subdomain/domain of the request and not the redirected server and port, but he put me on the right path to Google up a solution using VirtualHost and I finally found a solution that included the use of mod_proxy.

<VirtualHost *:80>
    ProxyPreserveHost On

    # setup the proxy
    <Proxy *>
        Order allow,deny
        Allow from all
    ProxyPass / http://localhost:8888/
    ProxyPassReverse / http://localhost:8888/
share|improve this answer
Thanks - this also worked for me - after searching for a long time. – DominikAngerer Jan 8 '15 at 22:03
For everyone who this answer didn't work for, keep in mind that you have to enable mods mod_proxy as well as proxy_http. – matewka Nov 20 '15 at 19:47
Is there something similar for IIS? – sємsєм Jul 6 at 16:36

Assuming that can be resolved to's IP, you could add the following to your httpd.conf:

NameVirtualHost *:80

<VirtualHost *:80>
    redirect /

Relevant Apache documentation:

  1. Guide to creating name-based virtual hosts
  2. Core, including VirtualHost and NameVirtualHost
  3. Redirect

Related question: Apache redirect based on hostname

(Note: the original version of this answer incorrectly suggested the use of RedirectMatch, which, as @ChrisS helpfully pointed out, cannot parse the domain portion of the URL.)

share|improve this answer
see my self provided answer for what I actually used, which is this idea of VirtualHost with mod_proxy to preserve the original host instead of doing a redirect. This is an internal server so I am not concerned with security or exploits of mod_proxy. – Jarrod Roberson Oct 28 '10 at 15:38
Found numerous other suggestions but this ultimately worked for me on Windows Server 2008 R2/Apache 2.2.25. – HPWD Jul 12 '15 at 20:07

Add in your main vhost configuration the following lines:

ProxyPreserveHost On
ProxyPass /
ProxyPassReverse / http://example:8080/

Note that this requires mod_proxy on Apache.

share|improve this answer
This is not a redirect; it proxies the connection. Enabling mod_proxy can be extremely easy to exploit if you aren't very careful configuring it. I would highly recommend against this. – Chris S Oct 28 '10 at 12:38
He doesn't want a redirect, as per his OP. He wants the original URL to remain in the address bar; this means using either mod_proxy or mod_rewrite, and y'all better avoid mod_rewrite. – adaptr Mar 1 '12 at 14:40

You're looking for mod_rewrite. Here's the link to Apache's documentation which includes many examples for basic and advanced configurations..

And if you're unable to interpret the documentation yourself, try adding this to httpd.conf:

RewriteEngine on
RewriteCond %{HTTP_HOST} ^dev\.example\.com$ [NC]        
RewriteRule ^(.*)$$1 [R=301]    

And if that's not a clear example, here's a link to a mod_rewrite beginners guide too.

share|improve this answer
It isn't correct. mod_rewrite should only be used as a last resort, when nothing else will do. The redirect and proxy solutions given are far superior in this (and almost any other conceivable) case. – adaptr Mar 1 '12 at 14:38
@adaptr This does a redirect, I fail to see how any of the other redirects are "far superior". And suggesting that he setup a proxy when he clearly doesn't have a firm grasp of Apache/Security/Performance/etc, is that serious? – Chris S Mar 1 '12 at 15:28

Run the following line on terminal (specify your domain and sub domain name correctly)

sudo nano /etc/apache2/sites-available/ 

Paste the following code and change as your requirement

<VirtualHost *:80>
        ProxyRequests Off

        #ProxyPass / http://localhost:8080/
        <Location />
                ProxyPreserveHost On
     # Uncomment the line below if your site uses SSL.
     #SSLProxyEngine On

Run the following lines on terminal (specify your domain and sub domain name correctly)

sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod
sudo service apache2 restart
share|improve this answer
Is there any essential difference between this and the accepted answer? – kasperd Jan 18 at 10:13
Most of the people forget to add sudo a2enmod proxy_http so they face difficulties on running properly. Also I try to give full process from start to end in a sequence to help more acculturate. Thanks for your question. – M A K Ripon Jan 18 at 10: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.