Using WWW proxy for server requests only.

[tmpease]

I have a WWW proxy bound to an external interface. All I want the service to do is to handle a Server Request to "Redirect client to predetermined location".

I set "Users can access this service" to "system policies are ignored" (with no users/groups listed) in an attempt to block all proxy use. No authentication methods (Basic/Java) are checked. I also tried to also set a policy for everyone with the Advanced criteria "Is Non-Proxy is True."


Upon a non-proxied connection, a "http://" session is created which eventually times out, and an "authentication failed" system message is issued, then the redirect is issued corrrectly. Proxied connections create an http:// session that times out, and eventually the proper error result is issued.

This is undesired behavior (a bug in my book).


Is there a better way to use wingate to merely issue HTTP-302 messages?


Thank you for your time.

[adrien]

I have a WWW proxy bound to an external interface. All I want the service to do is to handle a Server Request to "Redirect client to predetermined location".

I set "Users can access this service" to "system policies are ignored" (with no users/groups listed) in an attempt to block all proxy use. No authentication methods (Basic/Java) are checked. I also tried to also set a policy for everyone with the Advanced criteria "Is Non-Proxy is True."

If you have no policies (i.e. default ignored, and no others added) then all access to the service will be denied. So you will need at least one policy to allow any sort of access.

When you created this other policy, which mandated that the request must be a non-proxy request, did you have any other requirements for the policy (i.e. authentication required etc)?

Upon a non-proxied connection, a "http://" session is created which eventually times out, and an "authentication failed" system message is issued, then the redirect is issued corrrectly. Proxied connections create an http:// session that times out, and eventually the proper error result is issued.

This is undesired behavior (a bug in my book).

Is there a better way to use wingate to merely issue HTTP-302 messages?

Thank you for your time.

The only thing that speaks HTTP in WinGate is the WWW Proxy, so if all you want is for any incoming connection to be redirected, then it will have to be the HTTP proxy... I think you are on the correct track. I would expect that the correct setup would be as you described it, e.g.

1. Single policy, with advanced set to single filter, single criterion "Is non-proxy request is TRUE"
2. On the non-proxy request tab, set to "redirect to ..."

That should be it.

Adrien