SummaryIn situations where there is no policy involving HTTP traffic, the Exinda is not caching any content.
OverviewWhen enabling a policy for a specific application (ie, iOS Updates or Youtube), no caching is seen - including no blue striping on the real time monitor and no reduction under the optimization graph. In this scenario, there is no specific 'web' policy (or policy for HTTP) that has caching enabled on it.
CauseIn order to cache any content, the very first packet of the conversation needs to be intercepted by a policy enabled with Edge Cache. Since HTTP is a TCP based application, the very first packet is always a TCP_SYN which does not contain any Layer 7 information. The policy where the very first packet of any Internet Based traffic falls under is ALWAYS the HTTP policy (Typically a policy involving the 'Web' application group), regardless of whether the traffic is Youtube, Facebook, common browsing or Software Updates.
Ensure Edge Cache is enabled in the policy where regular HTTP traffic falls. Make sure the policy is added to a virtual circuit so that traffic can match with it and Edge Cache can do its caching, and ensure that the virtual circuit's direction is either 'Outbound' or 'Both'.
Occasionally it is necessary to restart the Edge Cache service to begin catching traffic. This can be done under Configuration > System > Optimization > Services.
If you are still not able to see new flows hitting the Edge Cache engine open a case with Exinda Support for further investigation.