Issues with caching in Wingate 5.2.3

[fcosentino]

Guys,

we are having so many troubles with caching in Wingate that I was forced to disable it, losing one of the main features of a proxy server.

Basically, it is incompatible with many .ASP & .JSP pages and websites.

I excluded .ASP and .JSP pages from cache by setting a rule in the inbound (what to cache) and on the outboud (what to purge) with NO results whatsoever (are you sure that those rules work at all???).

For example, the https://www.managedonline.optusbusiness.com.au returns an error every time you click "next" to go to the next step of the wizard for bills reporting. By retrying multiple times, occasionally it works. When caching is off, it works. Tried from Squid 2.4, it works fine.

Another website that simply doesn't work, producing even cross-credentials between users after authentication is https://fluidpower.au.eaton.com - One user logons, the next user gets into the site and gets the previous user credentials.

Is there any chance for you to revisit the caching engine and make it more compatible with most of the websites? I am getting so many complaints from users every time I switch it on that it is absolutely unacceptable.

[ArtimasZ]

I have similar problems. it's either i'm not setting the rules correctly -or- the cache is messed up if you use rules. I had mine set up for only caching images, however it looked like it was still caching whole pages because i would have to rebuild the index sometimes to get current sites.

Now, i just don't use proxy services what so ever, and went with straight nat...

[fcosentino]

Even by disabling the caching, I am experiencing still similar issues - less frequently, though.

Is 5.2.3 broken for HTTPS???