Kerio Tech KERIO WINROUTE FIREWALL 6, Руководство администратора

Страница: 126 / 368

Chapter 8 Configuration of network services
126
Warning
Changes in this entry will not be accepted unless the WinRoute Firewall Engine is
restarted. Old cache files in the original folder will be removed automatically.
Cache size
Size of the cache file on the disk. Maximal cache size allowed is 2 GB ( 2047 MB )
Note:
1. If 98 per cent of the cache is full, a so called cleaning will be run — this function
will remove all objects with expired TTL. If no objects are deleted successfully, no
other objects can be stored into the cache unless there is more free space on the disk
(made by further cleaning or by manual removal).
2. The maximal cache size is applied in WinRoute since 6.2.0 . In older versions, maximal
cache size allowed was 4 GB (the threshold was cut for technical reasons). If, upon its
startup, the WinRoute Firewall Engine detects that the cache size exceeds 2047 MB ,
the size is changed to the allowed value automatically.
3. If the maximum cache size set is larger than the free space on the corresponding
disk, the cache is not initialized and the following error is recorded in the
Error
log
(see chapter 22.8 ).
Max HTTP object size
maximal size of the object that can be stored in cache.
With respect to statistics, the highest number of requests are for small objects (i.e. HTML
pages, images, etc.). Big sized objects, such as archives (that are usually downloaded at
once), would require too much memory in the cache.
Cache Options
Advanced options where cache behavior can be defined.
• Continue aborted download — tick this option to enable automatic download of
objects that have been aborted by the user (using the Stop button in a browser).
Users often abort downloads for slow pages. If any user attempts to open the
same page again, the page will be available in the cache and downloads will be
much faster.
• Cache responses ’302 Redirect’ — this option accelerates connection to redirected
web pages.
Under usual circumstances, 302 Redirect responses are not cached. HTTP proto-
col’s return code 302 stands for temporary redirection — such redirection can be
canceled any time or the target URL can change. If user applies the cached re-
sponse to open a web page, the client can be redirected to an obsolete or invalid
URL.
•
Use server supplied Time-To-Live — objects will be cached for time specified by
the Web server from which they are downloaded. If TTL is not specified by the
server, the default TTL will be used (see the HTTP protocol TTL item).