Hot to tell cache not to cache .html files?

[toysareforboys]

I have Wingate 5.0.1 build 766, setup to be used as a transparent proxy. I have 300 gigs of cache, but there gets to be a problem where it's caching the .html files and not checking for newer ones, just always using the cached ones.

So, i'd like to stop of from caching .htm, .html, .php, etc. How do I do it?

Thanks.

-Jamie M.

[Nev]

I have Wingate 5.0.1 build 766, 8<... I have 300 gigs of cache, 8<... -Jamie M.

Hi -Jamie M,

Wow 300Gb!

You can upgrade to the latest version of Wingate with your existing licence, that will probably cure this for you.

[toysareforboys]

I would really hate to have to change the version. This setup has been working flawlessly for so long, even with the massive cache, other then the .html problem. So there is no way to add a filter or something to stop it from caching certian file extensions?

Thanks.

-Jamie M.

[jamesc]

*A few notes regarding 6.2.1 - the concepts should be able to applied to 5.x too.

1. Options shown in red denote how often to check for new version of HTLM or Other files.




2. Example policy not to cache any .htm pages

[toysareforboys]

When I set the filter like you have it in the picture, it still caches everything including htm files. When I remove the "not", then it only caches .htm files and nothing else??

-Jamie M.

[jamesc]

When I set the filter like you have it in the picture, it still caches everything including htm files

I would not expect it to - and when creating policies not to cache then all the criterions should be within the same filter.

When I remove the "not", then it only caches .htm files and nothing else??

Correct - after applying that filter only .htm files will be added to the cache (although what was already in there should still be available - if you wanted to purge all .html files from your current cache then create a purging policy).


Let the forum know if you are still having problems.

[rboynton]

I'm having a similar problem. I tried to exclude certain websites from the cache, but the cache is still being used (not seeing updates that I recently made to my website). An example of an exclusion is:

NOT HTTP URL Equals "http://www.radicaldebtelimination.com"

Do I have to make an explicit exclude for each subpage, or will this top level URL do (when it's working correctly)?

[logan]

Try changing your policy to:

NOT HTTP URL contains "radicaldebtelimination.com"


A URL consists of a hostname, a port (optional), a path, and a filename.
By making a policy that "equals" only the hostname of a website, any URL's that contain a path and filename will not match the policy and will still be cached.

e.g.
http://www.microsoft.com/en/us/default.aspx

If I made a criterion "NOT HTTP URL equals http://www.microsoft.com/", this website will still be cached because "http://www.microsoft.com/" does not equal "http://www.microsoft.com/en/us/default.aspx".

By changing the criterion to "contains - microsoft.com", you will cover almost all of the microsoft.com website. This also covers connections that navigate to the site without using "www." at the begining of the domain.