Cache Response Types

The "Cache Response" graph in the MAS Dashboard displays the states which a file can be in when the request for it is recorded in the MAS access log:

  • CACHE_HIT - The file was served from cached copy. No request was made against the origin server. Size recorded will be the number of bytes received by the client making the request.
  • CACHE_MISS_CACHE - The file was not found in the cache, therefore a request to origin was made and the content was pass-thru streamed to the end user while at the same time cached by MAS. Size recorded will be the number of bytes received by the client making the request.
  • CACHE_MISS_RECACHE - The file was not found in the cache, however a record of the file exists in cache memory. The file was re-downloaded from origin and the content was pass-thru streamed to the end user. Size recorded will be the number of bytes received by the client making the request. Note that this state is very rare. Should you find this state frequently in your logs, please contact technical support for immediate assistance.
  • CACHE_MISS_EXPIRED - The cache record indicates that the file has gone over the TTL (time-to-live) and has therefore expired. The file will be re-downloaded from origin and pass-thru streamed to the end user. Size recorded will be the number of bytes received by the client making the request.
  • CACHE_MISS_STREAM
    • For static content configurations: The cache record states the file is in "DOWNLOADING" state, probably from a previous "CACHE_MISS_CACHE". Since the file is already being cached, there is no need to create another cached copy on MAS. Since it is still downloading it is not useful to read the incomplete cached copy and send it back to the client. So we hit the origin server for this. Size recorded will be the number of bytes received by the client making the request.
    • For streaming content configurations: Our RTMP servers send out a heartbeat containing connection data every 3 seconds. For each RTMP connection in the PLAYING state, we create a log entry with the size reported as the number of bytes sent during the 3 second timeframe.
  • CACHE_MISS_SOURCE_FAILED - This response type is only valid for HLS requests in streaming content configurations. This state is reported when an edge server receives a request for a .ts or .m3u8 file and the file is not in edge cache. In which case, the edge cache will try to request the file from the MAS ingest server. If the ingest server reports that the requested file is not found (HTTP 404), then the edge server will report this in the logs as CACHE_MISS_SOURCE_FAILED.
  • CACHE_MISS_OTHER - The cache engine received an error while trying to retrieve content from origin. This indicates HTTP-related errors while connecting and trying to GET content from your origin server. For example, HTTP 4xx or HTTP 5xx errors.

Still need help? Contact Us Contact Us