Getting to Know the Media Control Center

Identifies all requests that were submitted to the CDN for your content.

Identifies requests that were served from CDN cache.

More Details

A cache hit identifies a request that resulted in one of the following cache status codes:

• In Cache - Cache Hits
• Revalidated Cache Hits
• Partial Cache Hits

Identifies requests that were served from an origin server instead of CDN cache.

More Details

A cache miss identifies a request that resulted in one of the following cache status codes:

• From Origin Cache Misses
• Expired-Updated Cache Misses
• Client Refresh Cache Misses

Indicates how the CDN handled the request with regards to caching.

View cache status code definitions.

The names for our existing cache status codes have been updated. Although these updated names are only being used by the Dashboard, we plan on rolling them out throughout the MCC.

Identifies the percentage of responses sent to the client for each HTTP status code series (e.g., 2xx, 3xx, 4xx, etc.). Each series contains all status codes that fall within that range. For example, 2xx includes all status codes that fall within the 200 - 299 range.

Original Name: UNCACHEABLE

This status is reported when an asset's Cache-Control and Expires headers indicate that it should not be cached on a POP or by the HTTP client. These types of requests are served from the origin server.

Original Name: NONE

This status indicates that a cache content freshness check was not performed. This check is skipped when Token-Based Authentication denies a request or when an HTTP request method is used that bypasses cache (e.g., PUT, DELETE, etc).

Original Name: CONFIG_NOCACHE

This status indicates that a customer-specific configuration on our edge servers prevented the asset from being cached.

For example, Rules Engine may prevent an asset from being cached by enabling the Bypass Cache feature for qualifying requests.

Original Name: TCP_CLIENT_REFRESH_MISS

This status is reported when an HTTP client (e.g., browser) forces an edge server to retrieve a new version of a stale asset from the origin server.

By default, our servers prevent an HTTP client from forcing our edge servers to retrieve a new version of the asset from the origin server. However, this behavior may be overridden by leveraging the Honor No-Cache Request feature (Rules Engine).

This status is reported when staleIdentifies cached content whose TTL has expired. Our edge servers revalidate stale content with the origin server. This step ensures that the latest version of the requested content is served to the requester. content is requested. This metric is calculated by summing requests that result in either of the following cache status codes:

• Revalidated Cache Hits
• Expired-Updated Cache Misses

Original Name: TCP_EXPIRED_MISS

This status is reported when a newer version of an expired cached asset is served from the POP to the client. This occurs when the TTL for a cached asset has expired (e.g., expired max-age) and the origin server returns a newer version of that asset. This new version of the asset will be served to the client instead of the cached version. Additionally, it will be cached on the edge server and the client.

Original Name: TCP_MISS

This status indicates that a cached version of the requested asset was not found on the POP closest to the client. The asset will be requested from either an origin server or an origin shield server. If the origin server or the origin shield server returns an asset, it will be served to the client and cached on both the client and the edge server. Otherwise, a non-200 status code (e.g., 403 Forbidden, 404 Not Found, etc.) will be returned.

Original Name: TCP_HIT

This status is reported when a request is served directly from the POP to the client. An asset is immediately served from a POP when it is cached on the POP closest to the client and it has a valid TTL. TTL is determined by the following response headers:

• Cache-Control: s-maxage
• Cache-Control: max-age
• Expires

This status is reported when the CDN was prevented from serving content from cache due to either of the following types of configurations:

• CDN: This type of request is tracked through the CDN Overrides - Not Cached cache status code.
• Origin Server: This type of request is tracked through the Bypass Cache - Not Cached cache status code.

Original Name: TCP_PARTIAL_HIT

This status is reported when a request results in a hit for a partially cached asset. The requested asset is immediately served from the POP to the client.

The Partial Cache Sharing feature enables the capability to generate partially cached content.