Content delivery network (CDN) content server request handling mechanism with metadata framework support
First Claim
1. Apparatus, comprising:
- a hardware processor;
a data store storing a host configuration table (HCT) that identifies content provider domains or subdomains that are being managed by a content delivery network service provider (CDNSP), wherein at least one entry in the HCT comprises a content provider domain or subdomain that is aliased to a CDNSP domain, the at least one entry pointing to a configuration file associated with the content provider domain or subdomain, the configuration file having at least one content handling instruction associated therewith;
computer program instructions executed by the hardware processor for;
receiving a request for a content object, the request being received from a client as a result of a DNS query to a content provider domain or subdomain being resolved using the CDNSP domain in lieu of the content provider domain or subdomain, the request for the content object having a host header associated therewith, the host header including a name value;
determining with the name value in the host header matches any content provider domain or subdomain entry in the HCT;
if the name value in the host header matches any content provider domain or subdomain entry in the HCT, retrieving the configuration file;
applying the content handling instruction in the configuration file; and
after the content handling instruction is applied, serving the content object in response to the request.
5 Assignments
0 Petitions
Accused Products
Abstract
To serve content through a content delivery network (CDN), the CDN must have some information about the identity, characteristics and state of its target objects. Such additional information is provided in the form of object metadata, which according to the invention can be located in the request string itself, in the response headers from the origin server, in a metadata configuration file distributed to CDN servers, or in a per-customer metadata configuration file. CDN content servers execute a request identification and parsing process to locate object metadata and to handle the request in accordance therewith. Where different types of metadata exist for a particular object, metadata in a configuration file is overridden by metadata in a response header or request string, with metadata in the request string taking precedence.
-
Citations
11 Claims
-
1. Apparatus, comprising:
-
a hardware processor; a data store storing a host configuration table (HCT) that identifies content provider domains or subdomains that are being managed by a content delivery network service provider (CDNSP), wherein at least one entry in the HCT comprises a content provider domain or subdomain that is aliased to a CDNSP domain, the at least one entry pointing to a configuration file associated with the content provider domain or subdomain, the configuration file having at least one content handling instruction associated therewith; computer program instructions executed by the hardware processor for; receiving a request for a content object, the request being received from a client as a result of a DNS query to a content provider domain or subdomain being resolved using the CDNSP domain in lieu of the content provider domain or subdomain, the request for the content object having a host header associated therewith, the host header including a name value; determining with the name value in the host header matches any content provider domain or subdomain entry in the HCT; if the name value in the host header matches any content provider domain or subdomain entry in the HCT, retrieving the configuration file; applying the content handling instruction in the configuration file; and after the content handling instruction is applied, serving the content object in response to the request. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
Specification