Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

Proxy Caching Problem

Mar 02 04 3:20 pm

Hi All

I'm having trouble getting wingate to cache pages properly. DNS/NAT are working fine, can do nslookup from class B NAT to the net but http requests only seem to partially load most sites. Once a site is loaded on one client machine it should be in cache and therefore load from the proxy very quickly...unfortunately this is not this case for some reason???
Webpages only partially load until you click stop in the browser then more of the page is displayed. Any ideas on configuration settings that would cause this?

Mar 02 04 3:41 pm

A few questions, to get a clearer picture of your configuration:

1. Which version of WinGate are you running ?
2. Are you running any data scanning plugins (PureSight / Kaspersky AV) and are any of them enabled ?
3. Do you have any specific caching criteria specified (Purging, etc.)

Re: Proxy Caching Problem

Mar 02 04 4:54 pm

Hi

Thanks for the reply. Here is some info on the specific details. Im running Wingate on a W2K box which has dual NIC's with static WAN IP, Class B LAN using NAT on the other NIC. The PC is also running NAV corp 8.1 to update clients on the private network. I'm currently running Wingate version 5.2.2 (Build 892), also running AV filter 4.0.1.19 (visnetic) and gatefilter 1.1. All services are started and running.

As far as caching goes i've set it to "cache everything" up to 1GB. haven't set any purge settings. Clients can recieve http requests but wont load the full page in most of the time. I thought it might be something to do with timeout configs but i've got that set to 10 seconds. Any ideas???

Cheers

Mar 02 04 5:00 pm

That sounds like a plugin problem. I assume you have Transparent Redirection on ? (In the appropriate WWW Proxy, you have "Redirect WGIC/NAT sessions" ticked)

Would it be possible for you to run a test with the plugins disabled for the WWW proxy service ? The easiest way to do this (Without affecting normal operation) would be to create a second WWW Proxy Service on say, port 81. Disable plugins for that Proxy Service and connect one client to that. (In the browser, specify the appropriate IP+port 81)

If you don't have any problems with caching then, we might have to investigate if either of the plugins could be causing your problem.

RE: Proxy Caching Problems

Mar 02 04 7:11 pm

Hi

Yes i had already enabled transparent re-direction & Redirect WGIC/NAT sessions. Disabled the plugins, saved config then stopped/started the wingate engine. I ran the test on Port 80 as other ports are blocked @ the perimiter router. The problem still persists even without plugins. when proxy clients try to access a page it won't fully load until you click stop in the browser and then click refresh. Interesting to note that nslookups from proxy clients are instant which leads me to think DNS & NAT are working fine and my problem is with caching?. The local browser settings are configured not to check for a newer version of the page. Any ideas? Thanks for your help
Post a reply