Webservers sharing a port

[flyswatta]

By using the ProxyPass you leave your other apps running in whatever application they were in before - that way you're not cobbling something together. You're just letting the Proxy server go serve the request on behalf of the client, then the proxy returns the results to the client.

[McBainUK]

So you're saying I could run IIS with ASP, behnd Apache?

[flyswatta]

So you're saying I could run IIS with ASP, behnd Apache?

More like alongside it. Usually you use ProxyPass with another server in the mix. Let's use this as an example:

Firewall (port 80 open) --> webserver (apache w/ProxyPass) --> other web server (IIS, GBPVR, Utorrent, whatever)

The request from the client goes to port 80 on the firewall, gets sent to the Apache web-server. The apache web server then proxies the request, in other words, the apache server initiates a request on behalf of the client to the "other web server". The result gets returned to the Apache web server, who in turn, replies to the client. The important distinction is that the client never directly accesses the "other web server".

This concept should work on the same host. I've got an apache web server already set up. I'll play with it and see if I can receive an inbound port 80 request and ProxyPass it to my GBPVR web interface (on port 8080 for me). If I get it working, I'll post the exact syntax for you.

[Koenie]

Yes, That is (more or less) what I do. My incoming server is apache, dealing with some straightforward web pages and forwarding the EWA stuff to the GBPVR webserver (I used to run IIS for this but after a reinstall last week I do not get it to work any more - needs some work). Some other applications to their respective servers.

Currently I have the EWA working trough a rewriterule though as I did not manage to proxy it. I use subdomains to detect where the request has to go but do not manage to proxy for GBPVR.

Flyswatta could you explain how to get the proxy working. incomming is gbpvr.domain.com which has to go to localhost:7467/gbpvr. Till now I do not manage to get this working as the proxy stumbles over the addition of a directory. Any ideas how this could be made to work? (this way I do not need to keep port 7467 open).

Flyswatta you were quicker than me so just take is as a second for the question.

[Torque]

In IIS, you can could create a "website" for each port and point the home directory to the app for that port. Then setup up redirects on the default site, port 80, so you don't have to type in the port numbers.

http://www.mcbainuk.com/gbpvr (on port 80) redirects to:
http://www.mcbainuk.com:7654 (root = /gbpvr)

http://www.mcbainuk.com/utorrent redirects to:
http://www.mcbainuk.com:8080 (root = /utorrent)

[flyswatta]

Okay, got it. Apparently there is a "fat finger" in the httpd.conf file if you use xampp :mad:

Anyway, for Apache 2.2, uncomment the following LoadModule lines:

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.soLoadModule

At the bottom of your httpd.conf file, add the following (between the lines).
Change the port numbers to your port numbers

#--------------------------------------------
ProxyRequests Off

<Proxy *>

Order deny,allow
Allow from all

</Proxy>

# GBPVR Web UI
ProxyPass /gbpvr http://localhost:8080/gbpvr
ProxyPassReverse /gbpvr http://localhost:8080/gbpvr

# uTorrent Web UI
ProxyPass /gui http://localhost:85/gui
ProxyPassReverse /gui http://localhost:85/gui
#--------------------------------------------

WARNING: the request to gbpvr is coming from the localhost, so if you don't have security set to prompt from login on local LAN, then everyone on the internet will get right in to your web ui.

[flyswatta]

In IIS, you can could create a "website" for each port and point the home directory to the app for that port. Then setup up redirects on the default site, port 80, so you don't have to type in the port numbers.

http://www.mcbainuk.com/gbpvr (on port 80) redirects to:
http://www.mcbainuk.com:7654 (root = /gbpvr)

http://www.mcbainuk.com/utorrent redirects to:
http://www.mcbainuk.com:8080 (root = /utorrent)

I think the idea was that port 8080 and port 7654 are blocked at the firewall. They wanted to access all of the different applications on the application native ports via the internet on port 80.

[Torque]

ahh yes, i read right past that. Then a proxy would be needed.

Ignore me

[bgowland]

Seems a bit of an overkill to install Apache just for its proxy capabilities if you also have to run another web server (IIS or whatever) to give the ASP support. A lightweight proxy server on its own would seem more sensible.

Cheers,
Brian

[McBainUK]

A lightweight proxy server on its own would seem more sensible.

Any suggestions?