by adrien » May 12 14 10:46 am
Hi
WinGate supports proxying in the case you mention, however you need to enable it in the web proxy under the "web server" tab. In that tab the default "site" determines by default what happens when a server-style request is received by WinGate.
When you're diverting connections to WinGAte from a router, the connection and request appears to WinGate as a server request - where the client is making a request that treats WinGate like a server (the form of the request line in an HTTP request is different between requests to servers and requests to proxies).
So you just set the action for the default site to be "Proxy". This causes WinGate to use the host header to determine where to connect, since the original source IP information is lost in the forwarding (unless the router is routing via WinGate instead of forwarding connections to it - in which case WinGate's standard intercepting config will work).
As for WinGate using all the resources. WinGate is a 32 bit app, so won't use all that RAM, but there's no limit to the amount of disk space WinGate will use - you can set up any number of cache volumes.
One reason you may be seeing a reduced hit-count in squid though may not be due to squid itself, but more to do with how sites are changing. For instance many sites are now https only, or go to more and more extreme lengths to suppress caching. If you want to cache https traffic, you'd need to turn on https inspection, and that won't work with forwarded connections - the clients need to be configured to use the proxy, and have a certificate installed etc.
Regards
Adrien