Wingate 5.0.5 caching problems

[timr]

We are running Wingate 5.0.5 without the Wingate proxy client. One of the web sites we try to go to requires a web based username & password, and once we log in we get a message saying that our session has expired.

The people running the website believe this is some type of caching problem with our proxy. They do not require any additional ports other then standard web traffic.

Within the caching tab, under "What to Cache" I have setup a filter which reads as follows (IP masked to protect the innocent)
NOT Server IP address equals "xxx.xxx.xxx.xxx"
However wingate is still caching the requests, because if I go around the proxy and erase my local disk cache it works fine.

[erwin]

Hi Tim

Do you have the Intercepts/Transparent redirection turned on (found under the sessions for the WWW proxy).

This is required if your clients are using NAT or WGIC connection, so they can use the function and be affected by the cache.

I take it from your description the clients local disk cache is clean when you attempt to test your caching restriction through WinGate. Just making sure there isnt affecting things on the client side.

Regards
Erwin