Content delivery network (CDN) content server request handling mechanism with metadata framework support

• US 8,484,319 B2
• Filed: 02/20/2012
• Issued: 07/09/2013
• Est. Priority Date: 04/14/2000
• Status: Expired due to Term

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Wein, Joel M., Karger, David R., Kloninger, John Joseph, Lisiecki, Philip A., Nottingham, Mark C.
• Primary Examiner(s): Ibrahim, Mohamed
• Application Number:
  US13/400,146
• Publication Number:
  US 20120151016A1
• Time in Patent Office: 505 Days
• Field of Search: None
• US Class Current: 709/219
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 65/1063 Application servers providing network services systems providing special services to telephonic subscribers H04M3/42
• CPC Class Codes: H04L 65/61 for supporting one-way streaming services, e.g. Internet radio
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1006 with static server selection, e.g. the same server being selected for a specific client
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30

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.

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 whether 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.

2. The apparatus as described in claim 1 wherein the content object is one of:

a markup language page, an embedded object of a markup language page, a media file, and a software download.

3. The apparatus as described in claim 1 wherein if the name value in the host header does not match any content provider domain or subdomain entry in the HCT, the computer program instructions provide a response to the request for the content object, wherein the response provides an indication that the content object is not available to be served.

4. The apparatus as described in claim 1 wherein the computer program instructions also are executed by the hardware processor to receive and store the HCT in the data store.

5. The apparatus as described in claim 1 wherein the data store is computer memory.

6. The apparatus as described in claim 1 configuration file is distinct from the HCT.

7. The apparatus as described in claim 1 wherein the content handling instruction specifies whether the content object is to be cached and, if so, for how long.

8. The apparatus as described in claim 1 wherein the content handling instruction specifies an origin server from which an instance of the content object can be retrieved.

9. The apparatus as described in claim 1 wherein the content handling instruction specifies data associated with the content provider domain or subdomain for accounting purposes.

10. The apparatus as described in claim 1 wherein the content handling instruction specifies data that enforces a given authentication method.

11. The apparatus as described in claim 1 wherein the content handling instruction specifies data that enforces a given access control method.