Apps that are their own web servers all sharing port 80?

[jtusa]

I have a few different things on the server I want to be able to get to via the web. DVArchive, Browseamp(web control plugin for winamp), plus the IIS web server.

DVArchive and Browseamp are their own webserver, they don't just create a page that you can link in IIS, so you set the port through the respective programs. However, I want to be able to get to all of them through port 80 because where I'm usually hitting them from, port 80 is the only open one, every other port is firewalled.

Is there an app, script, piece of code I can use that will allow me access everything through that single port without conflict? Let me know if that doesn't make sense and I'll try to explain it a little better.

 

[n0cmonkey]

Use a proxy. Apache might work.

 

[Cheetah8799]

I understand what you are saying, but if they all listen to port 80 as their own "web server", then I don't think it'll work at all. You can probably configure each to listen on a different port, say 80, 81, 82, etc. Then try to get the firewall opened for the server IP and those ports. I guess that would be my suggestion.

If you dig around the web you might find some CGI scripts that make a web server act like a proxy. Sorry I dont' have any direct URLs to give. Basically the way you could get that to work is setup Apache or IIS to run on port 80 and make the script available. Then the user connects to that script with a URL like http://somesite.com/cgi-bin/proxy.cgi?internalsite=http://somesite:81/index.html. Those long nasty URLs could be setup with a direct link and frames in the main port 80 site if you really wanted. I know it gets messy, but it might work. :/

 

[jtusa]

Originally posted by: Cheetah8799
I understand what you are saying, but if they all listen to port 80 as their own "web server", then I don't think it'll work at all. You can probably configure each to listen on a different port, say 80, 81, 82, etc. Then try to get the firewall opened for the server IP and those ports. I guess that would be my suggestion.

If you dig around the web you might find some CGI scripts that make a web server act like a proxy. Sorry I dont' have any direct URLs to give. Basically the way you could get that to work is setup Apache or IIS to run on port 80 and make the script available. Then the user connects to that script with a URL like http://somesite.com/cgi-bin/proxy.cgi?internalsite=http://somesite:81/index.html. Those long nasty URLs could be setup with a direct link and frames in the main port 80 site if you really wanted. I know it gets messy, but it might work. :/

That makes sense, I'll see what I can dig up. Thanks.

 

[n0cmonkey]

Originally posted by: jtusa4

Originally posted by: Cheetah8799
I understand what you are saying, but if they all listen to port 80 as their own "web server", then I don't think it'll work at all. You can probably configure each to listen on a different port, say 80, 81, 82, etc. Then try to get the firewall opened for the server IP and those ports. I guess that would be my suggestion.

If you dig around the web you might find some CGI scripts that make a web server act like a proxy. Sorry I dont' have any direct URLs to give. Basically the way you could get that to work is setup Apache or IIS to run on port 80 and make the script available. Then the user connects to that script with a URL like http://somesite.com/cgi-bin/proxy.cgi?internalsite=http://somesite:81/index.html. Those long nasty URLs could be setup with a direct link and frames in the main port 80 site if you really wanted. I know it gets messy, but it might work. :/

That makes sense, I'll see what I can dig up. Thanks.

I think most of this functionality is available under Apache. I'd look at getting better utilities though, that kind of bahaviour is horrid.

 

[jtusa]

Originally posted by: n0cmonkey

Originally posted by: jtusa4

Originally posted by: Cheetah8799
I understand what you are saying, but if they all listen to port 80 as their own "web server", then I don't think it'll work at all. You can probably configure each to listen on a different port, say 80, 81, 82, etc. Then try to get the firewall opened for the server IP and those ports. I guess that would be my suggestion.

If you dig around the web you might find some CGI scripts that make a web server act like a proxy. Sorry I dont' have any direct URLs to give. Basically the way you could get that to work is setup Apache or IIS to run on port 80 and make the script available. Then the user connects to that script with a URL like http://somesite.com/cgi-bin/proxy.cgi?internalsite=http://somesite:81/index.html. Those long nasty URLs could be setup with a direct link and frames in the main port 80 site if you really wanted. I know it gets messy, but it might work. :/

That makes sense, I'll see what I can dig up. Thanks.

I think most of this functionality is available under Apache. I'd look at getting better utilities though, that kind of bahaviour is horrid.

Well the reason I'm doing this is that I've got all the stuff I want to get to, but at work ports are blocked so I can't get to it all.

 

[wkinney]

assign the other two to 443 and 21, which should be open in the firewall.

 

[kamper]

I believe n0cmonkey's on the right trail. Run the other two webservers on different ports, then lookup the mod_proxy documentation for apache. You should be able to map certain url patterns to localhost:someotherport so that something like:

http://yourserver/dvarchive/foo.bar

actually goes to

http://localhost:81/foo.bar

behind the scenes. Where localhost is the server machine and 81 is the port you're running dvarchive on. Much more elegant and transparent to the user.