LevelBlue Knowledge Base

KB Home Search Latest Additions Most Popular

Knowledgebase

Home » Knowledgebase » Legacy Products » Secure Web Gateway » ICAP » FAQ: Why is ICAP client as cache proxy not caching content?

FAQ: Why is ICAP client as cache proxy not caching content?

Show/Hide Article Tools

Question
In ICAP topology, the ICAP client is also used as a caching proxy. However some of the content is not being cached. Why is this and how can it be solved?

Answer
In specific situations some of the content is not cached when using caching proxy and Vital Security Appliance as an ICAP server.

When using the Vital Security NG Appliance as an ICAP server with a caching proxy.

Any content request which gets the status page will not be cached on the caching proxy.

In order to have specific content cached on the caching proxy we should disable
the status page examination for this specific content.

In order to do so, please perform the following steps:

Log in to the Management Console.
Navigate to Settings -> Miscellaneous -> Status page.
Set the required content types to be cached under the ‘Don't Activate if Content Type includes following substrings’ text box.

Software Version
8.3.x
8.4.0

This article applies to:: NG 1000; NG 5000; NG 8000

This article was previously published as:
Finjan KB 1156

To contact LevelBlue about this article or to request support:

Create a case through the Fusion portal (U.S. Government customers, use the TGS Fusion portal).

Call us on a local phone number.

Rate this Article:

Tags:
8.3.5, NG 1000, NG 5000, NG 8000, status page

Add Your Comments

Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster.

Execution: 0.037. 8 queries. Compression Disabled.