Does SurfFast always work exactly as configured? Does it make mistakes?
SurfFast is designed to filter, or block, content based on a number of filters, including by location, content properties (i.e. content type, file size, extension), PICS, specific keywords and more. Each of these filters can consist of a number of specific rules, which tell the filter exactly what to block. For example, you can create a rule, via the content properties filter, to block all resources that either have the .exe extension (Microsoft Windows executables) or are larger than 1M in size. The filters themselves, as far as we have been able to test, work as advertised. It is, however, possible that there are unknown bugs lurking in the implementation code that could cause certain content to bypass a specific filter. The tricky part of configuring filters, then, lies in defining a strong and effective rule set; this is where “mistakes” could occur. And unless your rules match the properties of the content to be blocked 100% of the time, certain content will occasionally slip thro
Related Questions
- One of the sites that I visit uses a cookie to keep track of my login, and enables it for two weeks. Can SurfFast be configured to delete the cookie when I exit from the browser?
- Webserver 6.1 is configured for HTTP compression on demand. Why do I see that requests going through the weblogics proxy plugin (wl_proxy) are not being compressed?
- How are results tabulated and why could there possibly be mistakes or problems?
