View this page in English

Censornet - internet filtering on your terms

BECTA Accredited products VMWare Certified Virtual Appliance Members of the Internet Watch Foundation Shortlisted for the BETT 2008 Awards Computer Security Awards finalist
Chat online now or call +44 (0) 845 230 9590 for help & advice

Search knowledge base

Product specific

Home » Knowledge base » Policy Modification

Policy Modification

July 18, 2011 • Customer Services       
Synopsis

You may have just modified your policy and wondered why the change does not appear to be working. This article explains the likely cause.

Article

If you have recently modified a policy, but the change does not appear to have taken effect the most likely reason is related to the Cache Timeout setting.

By default, the Cache Timeout is set to 120 (seconds) or 2 minutes. Consequently, changes to policies take ~2 minutes to propagate to the filter.

You can modify this setting by going to System->Configuration->Database Cache Limits and change the Cache Timeout value. However, it is strongly recommended that you do not do so.

Related articles


Last modified on Mon, July 18, 2011 « Back