WWW Proxy with web server on another machine (WG 6)

[scalt]

Hello,

I recently installed Wingate 7 on my firewall. I host a website on a machine behind it so I set-up a WWW Proxy service so people from the internet can access it. To do this, I bound the proxy with my external adapter and my internal adapter, and set the "Action to take with non proxy request" to "Pipe to predetermined server" and entered to correct informations.

Everything works exept for the fact that I have a security problem. By binding the WWW Proxy to the external interface, it also handles PROXY requests from the external interface, which is not too good....

My question is, is there a way to allow non-proxy request from the external interface while denying proxy requests so my machine can't be used as a proxy by anybody on the internet.

Thank you

[kgoodknecht]

In your browser settings configure the bypass proxy settings, with the name that will resolve to the local IP of the local web server. You will either have to add the name of the site with the IP of the webserver (local IP) in your hosts file or use a local DNS server to add the record to.

[scalt]

I don't think you understood my question properly.

I am simply asking if there's a way to use the WWW Proxy Service on my firewall to ONLY pipe non proxy requests from the external interface (so then can access my web site) and block proxy requests on the external interface.

From the internal interface however, i would like to allow both types of requests

[kgoodknecht]

I don't think you understood my question properly.

I am simply asking if there's a way to use the WWW Proxy Service on my firewall to ONLY pipe non proxy requests from the external interface (so then can access my web site) and block proxy requests on the external interface.

From the internal interface however, i would like to allow both types of requests

External users to a web site hosted behind Wingate? use TCP mapping listening on port 80 listening on the external interface, then map it to the IP of the web server on port 80 (if that's the port the webserver is on).
This will also give internal users access to the website by the public IP (something that is not possible with NAT).