In previous releases, a special policy had to be installed to force YouTube videos to be cached. SGOS 6.5.x or later enables the CachePulse feature to cache YouTube videos without the need to install the policy manually.
In some cases, however, the ProxySG or Advanced Secure Gateway appliance still does not cache YouTube videos, even though the enabled CachePulse database is up to date. This article details how to troubleshoot this issue.
1. A valid license for CachePulse with the latest update downloaded
2. An SSL interception policy to intercept YouTube traffic
3. The following policy in order to prevent an unsupported_encoding error users browse to https://www.youtube.com using Firefox or Chrome (IE is not affected):
The following article goes into more details about the above policy: Users see Content Transformation Error Exception when browsing YouTube
If all of the above steps have been applied to configuration, YouTube video access should be cached. If the issue persists, take the following steps to further troubleshoot the issue:
Example of the access logs:
2017-04-13 04:13:52 5 10.10.10.10 200 TCP_HIT 91429 1071 GET https r3---sn-onfxq0-ntqe.googlevideo.com 443 /videoplayback ...
Note the cache hit codes like the one above - "TCP_HIT".