Web address without using the port number

[Xebix]

I have one server with apache2 running my main site (www.example.com). I have a separate application on the same server that has it's own web server running on a different port (www.example.com:8888). What would be the best way to make site2.example.com pull up the site running on www.example.com:8888?

 

[Whatsisname]

use virtual hosts and have a different domain name (or use a subdomain, like dev.example.com) that points to the same host IP, then run them both on the same port. Then have the site on the subdomain do a redirect to the different port number on some other server. Or ditch the other port entirely.

 

[Xebix]

Got it figured out. Here's the basic config that I used.

<VirtualHost *:80>
        ServerName http://site2.example.com
        redirect permanent / http://www.example.com:8888
</VirtualHost>

 

[tim_m]

Doesn't that just make http://site2.example.com go to http://www.example.com:8888, i.e. change the address in the browser's address bar? If that's ok then so be it. If not, you can look into setting up a reverse proxy with apache.
http://www.apachetutor.org/admin/reverseproxies

 

[Xebix]

It's OK for now. I'm just working on a personal site. Eventually, I would like to do something a little more elegant. Thanks for the info.

 

[pcbird]

reverse proxy's are definitly what you want want. I've got 4-5 application servers running behind an apache server that does reverse proxies to them.

site.com/app1 -> appserver1:8080
site.com/app2 -> appserver1:8081
site.com/app3 -> appserver1:8082/app3
site.com/app4 -> appserver1:8082/app3
site.com/app4 -> appserver2:8080
etc.

then if I need to move an app or point to an alternate appserver (maintenance, new hardware, etc) I don't have to tell the 500 folks using them to hit a different URL.

Best part is my apache server is the only one "publicly" available. The app servers sit off in their own sheltered space that the users couldn't get to if they happened to know their names.

 

[Xebix]

So I decided to go ahead and try setting up a reverse proxy. I've been searching around on how to do it and came up with the config below and enabled it with a2ensite, but I am getting a 500 internal server error. Looking in the error log, I see this:

[Thu Feb 17 13:41:38 2011] [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.

<VirtualHost *:80>
ServerName http://site2.example.com

        ProxyRequests Off
        ProxyPass / http://site2.example.com:22420/
        ProxyPassReverse / http://site2.example.com:22420/

 </VirtualHost>
~

 

[Xebix]

I figured it out. I didn't have proxy_http enabled.