| Solution | The content cache can be checked only when there is at least one virtual server with caching enabled.Below are the three methods to verify the content cache. Method 1 : > Login to the admin console and navigate to Activity > Content Cache.> To display the specific HTTP URL content, please add Host Header matching and Path matching.> Click Display.
 Once displayed, if the Hits column has number zero, it means the content is a response from the backend server.If the number under Hits column increases, it means the content received by client machine is cached in VTM. Method 2 : > Login to the admin console and ensure request tracing is enabled following the KB article : https://kb.pulsesecure.net/articles/Pulse_Secure_Article/6290/?kA1f1000000bnZK> Navigate to Activity > Connections.> Click Refresh Snapshot to refresh the connection analytics.> Click on the magnifying-glass icon for the specific HTTP URL. > Expand Request Tracing and check events.Once displayed, if the event HTTPCacheMiss (item not in cache) is present, it means the content is a response from the backend server.
 If the event HTTPCacheHit is present, it means the content received by client machine is cached in VTM.
 Method 3 : > Login to the admin console and navigate to System > Global Settings > Cache Settings.> Enable the setting for webcache!verbose: Yes.> Click Update. If HTTP response has header X-Cache-Info: set to caching, it means the content is a response from the backend server. If HTTP response has header X-Cache-Info: set to cached, it means the content received by client machine is cached in VTM. The HTTP response headers can be checked in Activity > Connections > Click magnifying-glass icon for a specific HTTP URL > Response Headers or it can also be checked in browser developer tools. |
|
|---|
