Caching Rules

[DSG]

Hello folks!

A customer of our company is using wingate since years, but is still not using the great caching option. They say, that caching can´t be used because of the danger to get not the most actual news (its a newspaper).

Now they realize, that their internet bill is geting larger from month to month because of higher and higher transfer volume. As i found out, with the purging rules i can nearly clear the cache as i like it, but that´s not the way i want to use. I would like it much more, to modify the caching rules.

After some tests i think i have found out which kind of rules i would like to get:

- some exclusions for specified urls
- exclusion for to small files (i think files smaller 40kb, 40960 bytes) should not be cached.

i don´t know why, but i don´t manage to realize this rules. For the first kind of exclusions i decided to the method "this criterion is nor met if http url contains %yahoo.com%". For the second exclusion i think "this criterion is not met if User: bytes received for client less than 40960". I don`t know why, but my rules don´t work, there are still files smaller than 40kb added to cache, and also the excluded urls are cached.

Can anybody help me? I think two filters should be right, one for the file size and one with the excluded urls, seperated in multiple criterions. Is this right or is this my problem?

Helpless greetings from germany
DSG

[ChrisH]

DSG - I would put those two criteria into one filter so that both must be met before item is cached. WG will logically .OR. the two filters. I believe you want to logically .AND. the criteria and WG will do that if you put both criteria into one filter. Let us know if it helps.

[DSG]

Hey Chris!

I just modified my test installation, but it seems that wingate is still caching small files. Because i´m a little bit out of training in the english language, i´ll ask you, if i understood you correctly.

As long as i but criterions into one filter they are logically combined. So all criterias must be met, before wingate starts caching? Hmm, so wouldn´t it be the right way to put it in seperated filters? One for the size alone and another one for the url? The next thing i´m not sure if i understood you rightly: If i want to exclude sites from caching, isn´t it correct to put every url into another filter? You wrote, that criterions in a filter are AND combined, so for example both url exclusions must be met (yahoo and aol) before wingate starts caching. If i want that both url strings are not cached for itself, i have to make two seperate filters, right?



Greetings from Germany in the middle of the night
Norbert

[ChrisH]

Norbert,

OK if you want more than one site NOT to be cached they all go in the same filter along with the NOT less than file size criteria.

e.g. Don't cache AOL
Don't cache Yahoo
Don't cache Microsoft
Don't cache less than 40K

Let's say you go to Qbik.com Because it's not AOL, Yahoo or Microsoft those criteria are met and assume the file is over 40K so that criteria is also met. From a logic point of view, since all criteria are met and are ANDed, the result is 1 so the site/file will be cached. Try this it should work. Let us know. It is getting later here too.

[DSG]

I don´t know why, but it still doesn´t work. Is there maybe still a little error in my idea? Is there any way to realize what is inside the cache of wingate?

Maybe we can so find out which files are inside the cache...


Best regards from germany
DSG

[ChrisH]

Hi Norbert,

How are the client computers connecting to the WG server? NAT,WGIC Proxy? ALso , after looking at this post again, your criteria for file size is not what the User: bytes received for client less than xxxxx is meant for. I am not sure if you can filter the cache file size.

[DSG]

Hey Chris!

I think that we have both the same assumption how the Wingate cache is working. I´ve already modified the customers purging and scheduler rules so, that all 6 hours all files smaller than 80kb or older than 3 months are automatically being purched.

So the cache folder doesn´t get to large and filled with to many and to small files. Since this modification, the server became much faster (what a wonder, now there not more than ~ 10.000 files in the folder) and the Windows filesystem doesn´t have a problem to cache the file access to the wingate cache file.


What´s your way to realize a fast and not to large proxy cache? All clients are using the usual browser method to connect over a proxy..

Norbert

[ChrisH]

Norbert,

I believe that you are on the right track wrt purging rules and cache size. I have no huge networks I administer and they are all on broadband so speed is quick and with the increasing amount of dynamic content on the web, honestly, caching is not a big issue for me with these setups. Having said that, if you pay for every byte your ISP sends to you, caching can certainly help to minimise those costs. Perhaps there are other WG users that can offer their caching expertise in your caching quest as mine is limited.

All the best