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

Strange Problems Caused by Cache

Jul 18 08 5:03 am

We had a couple of problems at one site:

- Calling Google with Internet Explorer would alternately go to either Google or the ISP's registration page.
- Radio station stream would not play.

The resolution was to stop Wingate and empty the Wingate\Cache directory.

5 days of tearing our hair out trying to figure out what was wrong and 2 minutes to clear the cache and resolve it.

Just in case anyone else has odd problems, maybe this info will help.

- Al
Last edited by alyork on Jul 19 08 5:22 pm, edited 1 time in total.

Re: Strange Problems Caused by Cache

Jul 19 08 3:45 pm

Hi Al,

You can specify 'what not to cache' in Wingate's Cache policy, such as 'not http url which contains - string' this can be useful perhaps to prevent the behaviour you experienced, which I must say I haven't seen myself.

Re: Strange Webpage Problems Caused by Cache

Feb 20 09 6:59 am

Thread title says it all so I thought I'd continue an old thread.

Several of our Wingate sites are experiencing Web pages being stuck or flipping back to old versions of the page. The stuck sympton happens on sites, such as MSN, where the same headlines from months ago show up every day. The flipping is when a refesh is done and and old page reappears, and another refesh brings back either the current page or a different old page and repeats over and over again. Another odd behaviour is when a signon fails and has to entered again as the initial signon page is presented a second time.

And magically, manually clearing the Wingate cache folder makes all the problems go away, for while.

Re: Strange Problems Caused by Cache

Feb 20 09 10:40 am

Hi

I'd also recommend changing the default settings under Rechecking. Set these both to 0.

Let me know if that helps.

Regards

Adrien

Re: Strange Problems Caused by Cache

Feb 28 09 2:06 pm

Setting the rechecking settings to 0 seems to have worked. - Al
Post a reply