Abstract: Techniques relating to caching a content object are disclosed. These techniques include transmitting, from a requestor to a first server, a revalidation request relating to a content object, and receiving, at the requestor from the first server, a response to the revalidation request indicating that the content object is not modified. The response is received at the requestor based on the first server determining that metadata describing one or more characteristics of the content object is stored in a cache associated with the first server and that the content object is not stored in the cache, and in response determining whether to retrieve content object data from any server based on analyzing a metric relating to retrieving the content object.

Abstract: Techniques relating to caching a content object are disclosed. These techniques include transmitting, from a requestor to a first server, a revalidation request relating to a content object, and receiving, at the requestor from the first server, a response to the revalidation request indicating that the content object is not modified. The response is received at the requestor based on the first server determining that metadata describing one or more characteristics of the content object is stored in a cache associated with the first server and that the content object is not stored in the cache, and in response determining whether to retrieve content object data from any server based on analyzing a metric relating to retrieving the content object.

Abstract: Techniques relating to caching a content object are disclosed. These techniques include transmitting, from a requestor to a first server, a revalidation request relating to a content object, and receiving, at the requestor from the first server, a response to the revalidation request indicating that the content object is not modified. The response is received at the requestor based on the first server determining that metadata describing one or more characteristics of the content object is stored in a cache associated with the first server and that the content object is not stored in the cache, and in response determining whether to retrieve content object data from any server based on analyzing a metric relating to retrieving the content object.

Abstract: Techniques relating to caching a content object are disclosed. These techniques include receiving, at a first server from a requestor, a revalidation request relating to a content object. The techniques further include determining that metadata describing one or more characteristics of the content object is stored in a cache associated with the first server and that the content object is not stored in the cache, and in response: determining, at the first server, whether to retrieve content object data from any server based on analyzing a metric relating to retrieving the content object, and transmitting from the first server to the requestor, based on analyzing the metadata, a response to the revalidation request indicating that the content object is not modified.

Abstract: The embodiments herein describe a CDN that uses revalidation to force edge servers to refresh their cached objects (i.e., download new copies of the objects from the origin data center). Revalidation can be used by edge servers to determine whether an object currently cached at the edge servers has been updated or changed in the origin data center. The embodiments herein leverage revalidation to perform a forced refresh to force the edge servers to refresh their cached object, regardless whether those cached objects match the objects stored in the origin data center. A forced refresh can be used when there is a network connection that may have caused the cached objects to become corrupted. Moreover, the forced refresh can be performed in batches so as not to overwhelm the network and computing resources in the CDN.

Abstract: The embodiments herein describe a CDN that uses revalidation to force edge servers to refresh their cached objects (i.e., download new copies of the objects from the origin data center). Revalidation can be used by edge servers to determine whether an object currently cached at the edge servers has been updated or changed in the origin data center. The embodiments herein leverage revalidation to perform a forced refresh to force the edge servers to refresh their cached object, regardless whether those cached objects match the objects stored in the origin data center. A forced refresh can be used when there is a network connection that may have caused the cached objects to become corrupted. Moreover, the forced refresh can be performed in batches so as not to overwhelm the network and computing resources in the CDN.

Abstract: Techniques relating to caching a content object are disclosed. A first server receives a revalidation request, relating to a content object, from a requestor. It is determined that metadata, relating to the content object, is stored in a cache associated with the first server. In response, the first server determines not to retrieve the content object from a second server. The content object is not stored in the cache. A response to the revalidation request, indicating that the content object is not modified, is transmitted from the first server to the requestor, based on analyzing the metadata.

Abstract: The embodiments herein describe a CDN that uses revalidation to force edge servers to refresh their cached objects (i.e., download new copies of the objects from the origin data center). Revalidation can be used by edge servers to determine whether an object currently cached at the edge servers has been updated or changed in the origin data center. The embodiments herein leverage revalidation to perform a forced refresh to force the edge servers to refresh their cached object, regardless whether those cached objects match the objects stored in the origin data center. A forced refresh can be used when there is a network connection that may have caused the cached objects to become corrupted. Moreover, the forced refresh can be performed in batches so as not to overwhelm the network and computing resources in the CDN.

Abstract: Techniques for improved media streaming are provided. A request for a variant list for streaming media content is received from a requesting entity, where the request includes a predefined flag. A set of predefined rules corresponding to the predefined flag is identified. The variant list is pruned based on the set of predefined rules, and the pruned variant list is transmitted to the requesting entity.

Abstract: Techniques relating to caching a content object are disclosed. A first server receives a revalidation request, relating to a content object, from a requestor. It is determined that metadata, relating to the content object, is stored in a cache associated with the first server. In response, the first server determines not to retrieve the content object from a second server. The content object is not stored in the cache. A response to the revalidation request, indicating that the content object is not modified, is transmitted from the first server to the requestor, based on analyzing the metadata.

Abstract: Techniques for improved media streaming are provided. A request for a variant list for streaming media content is received from a requesting entity, where the request includes a predefined flag. A set of predefined rules corresponding to the predefined flag is identified. The variant list is pruned based on the set of predefined rules, and the pruned variant list is transmitted to the requesting entity.