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

• US 20130297735A1
• Filed: 07/08/2013
• Published: 11/07/2013
• Est. Priority Date: 04/14/2000
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Wein, Joel M., Kloninger, John Josef, Nottingham, Mark C., Karger, David R., Lisiecki, Philip A.
• Granted Patent: US 9,160,704 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• 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. A computer program product in a non-transitory computer readable storage medium holding computer program instructions executable in a hardware processor, the computer program instructions comprising:

program code adapted to receive and store a data structure that identifies content provider domains, wherein at least one entry in data structure comprises a content provider domain that is aliased to an alternative domain, the at least one entry pointing to a configuration file associated with the content provider domain, the configuration file having at least one handling instruction associated therewith;

program code adapted to receive a request for a resource, the request being received as a result of a domain name service (DNS) query to a content provider domain being resolved using the alternative domain in lieu of the content provider domain, the request for the resource having a host header associated therewith, the host header including a name value;

program code adapted to determine whether the name value in the host header matches any content provider domain entry in the data structure;

program code adapted to retrieve the configuration file if the name value in the host header matches any content provider domain entry in the data structure;

program code adapted to apply the handling instruction in the configuration file; and

program code adapted to serve the resource in response to the request after the handling instruction is applied.

2. The computer program product as described in claim 1 wherein the resource is one of:

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

3. The computer program product as described in claim 1 wherein the handling instruction specifies whether the resource is to be cached and, if so, for how long.

4. The computer program product as described in claim 1 wherein the handling instruction specifies an origin server from which an instance of the resource can be retrieved.

5. The computer program product as described in claim 1 wherein the handling instruction specifies data associated with the content provider domain for accounting purposes.

6. The computer program product as described in claim 1 wherein the handling instruction specifies data that enforces a given authentication method.

7. The computer program product as described in claim 1 wherein the handling instruction specifies data that enforces a given access control method.