Scalable content delivery network request handling mechanism to support a request processing layer

• US 9,509,804 B2
• Filed: 12/19/2013
• Issued: 11/29/2016
• Est. Priority Date: 12/21/2012
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Stevens, Matthew J., Shotton, Frederick R., Chen, Tong
• Primary Examiner(s): Taylor, Nicholas
• Assistant Examiner(s): PENA-SANTANA, TANIA M
• Application Number:
  US14/135,179
• Publication Number:
  US 20140181187A1
• Time in Patent Office: 1,076 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/5051 Service on demand, e.g. definition and deployment of services in real time
• CPC Class Codes: H04L 41/509 wherein the managed service relates to media content delivery, e.g. audio, video or TV
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements

Abstract

Described herein are improved systems, methods, and devices for delivering and managing metadata in a distributed computing platform such as a content delivery network (CDN) so as to configure content servers to handle client requests. The teachings hereof provide, among other things, scalable and configurable solutions for delivering and managing metadata, preferably by leveraging dynamically obtained control information. For example, in one embodiment, a given content server may store metadata, e.g., in a configuration file, that references dynamic, late-bound control information for use in satisfying dependencies. This dynamic control information can be requested by the CDN content server, typically from a remote host, when needed to parse and execute the metadata.

Claims

1. A system, comprising:

a first server managed by a content delivery network (CDN) service provider and comprising circuitry forming one or more processors coupled to memory holding non-transitory computer-program instructions to be executed by the one or more processors to cause the first server to;

receive a first request from a client device over a network interface, the first request comprising an application programming interface (API) request;

in response to the first request, determine a configuration file stored at the first server to apply for handling the request, the configuration file defining any of;

recognized API endpoints and request forwarding instructions;

identify, within the configuration file, a content control that indicates how to handle the first request from within a set of content controls stored at the first server in the configuration file;

wherein the content control has a reference to an API endpoint content policy that controls, at least, request validation;

extract an identifier from the first request, the extracted identifier comprising any of (i) at least part of a URI, (ii) at least part of a hostname, and (iii) at least part of a request header field;

in response to the identification of the content control with the reference to the API endpoint content policy, send a second request that includes the extracted identifier to a remote host for the API endpoint content policy;

receive the API endpoint content policy from the remote host in response to the second request, the API endpoint content policy comprising at least one of;

(iv) an API resource model, and (v) an algorithm to compare the first request to an API resource model;

wherein the API resource model comprises at least one of;

(vi) designation of supported request methods, (vii) designation of valid URI path, (viii) designation of a valid URL query parameter resource, (ix) designation of arguments, parameters, or data necessary in requests;

(x) designation of a parameter or limit specified for a user;

apply the content control to the request at least by applying the API endpoint content policy to determine whether the first request conforms to the API resource model;

after applying the content control and the API endpoint content policy, send at least a portion of the first request to a second server, the second server being an API origin for the API;

the remote host comprising circuitry forming one or more processors coupled to memory holding non-transitory computer-program instructions to be executed by the one or more processors to cause the remote host to;

receive the second request from the first server, with the extracted identifier;

based at least in part on the extracted identifier, select the API endpoint content policy from amongst a plurality of API endpoint content policies stored at the remote host;

send the API endpoint content policy to the first server, in response to the second request;

wherein the first server is one of a plurality of distributed CDN servers, the first request is for a service accessible via the API, and the service enables any of;

(i) interaction with a multi-tenant storage system operated by the CDN service provider on behalf of content providers, (ii) interaction with a multi-tenant computing system operated by the CDN service provider on behalf of content providers, and (iii) configuration by a CDN user of a CDN content delivery service, said configuration comprising configuration of CDN features and services for delivering any of a website and a web application on the CDN user'"'"'s behalf over the CDN.

2. The system of claim 1, wherein the first request is directed to universal resource identifier (URI) that represents an API endpoint, the URI comprising any of a hostname and a path.

3. The system of claim 1, wherein the API resource model comprises any of:

a designation of supported request methods, an expected parameter, an expected argument, and expected data.

4. The system of claim 1, wherein the API endpoint content policy comprises any of a client identifier and data used for an authentication routine.

5. The system of claim 1, wherein the API endpoint content policy comprises logic for validating the first request.

6. The system of claim 1, wherein the API endpoint content policy calls a routine for any of:

authenticating and authorizing any of the client device, and an application executing thereon.

7. The system of claim 1, wherein the first server is one of a plurality of distributed CDN servers, the first request is for a service accessible via the API, and the service comprises a service provided by the CDN.

8. The system of claim 1, wherein the first server is one of a plurality of distributed CDN servers, the first request is for a service accessible via the API, and the service enables interaction with any of:

(i) a multi-tenant storage system operated by the CDN on behalf of content providers, and (ii) a multi-tenant computing system operated by the CDN on behalf of content providers.

9. The system of claim 1, wherein the first server is one of a plurality of distributed CDN servers, the first request is for a service accessible via the API, and the service enables configuration by a CDN user of a CDN content delivery service, said configuration comprising configuration of CDN features and services for delivering any of a website and a web application being delivered on the CDN user'"'"'s behalf over the CDN.

10. A system, comprising:

a first server managed by a content delivery network (CDN) service provider and comprising circuitry forming one or more processors coupled to memory holding non-transitory computer-program instructions to be executed by the one or more processors to cause the first server to;

receive a first request from a client device over a network interface, the first request comprising an application programming interface (API) request;

in response to the first request, determine a configuration file stored at the first server to apply for handling the request, the configuration file defining any of;

recognized API endpoints and request forwarding instructions;

identify, within the configuration file, a content control that indicates how to handle the first request from within a set of content controls stored at the first server in the configuration file;

wherein the content control has a reference to an API endpoint content policy that contains a reference to a credential content policy;

extract an identifier from the first request, the extracted identifier comprising a value in a token included in the first request sent by the client device;

in response to the identification of the reference of the credential content policy, send a second request that includes the extracted identifier to a remote host for the credential content policy;

a remote host comprising circuitry forming one or more processors coupled to memory holding non-transitory computer-program instructions to be executed by the one or more processors to cause the remote host to;

receive the second request for the credential content policy;

based at least in part on the extracted identifier, select the credential content policy from amongst a plurality of credential content policies stored at the remote host;

send the credential content policy to the first server in response to the second request;

the first server further being caused to;

receive the credential content policy from the remote host, the credential content policy comprising at least one of;

data used for a desired authentication routine, and an algorithm for performing an authentication check;

apply the content control to the request at least by applying the credential content policy to authenticate any of;

the client device, and a user thereof;

after applying the content control and the credential content policy, send at least a portion of the first request to a second server, the second server being an API origin for the API;

wherein the first server is one of a plurality of distributed CDN servers, the first request is for a service accessible via the API, and the service enables any of;

(i) interaction with a multi-tenant storage system operated by the CDN service provider on behalf of content providers, (ii) interaction with a multi-tenant computing system operated by the CDN service provider on behalf of content providers, and (iii) configuration by a CDN user of a CDN content delivery service, said configuration comprising configuration of CDN features and services for delivering any of a website and a web application on the CDN user'"'"'s behalf over the CDN.

11. The system of claim 10, wherein the first request is directed to universal resource identifier (URI) that represents an API endpoint, the URI comprising any of a hostname and a path.

12. The system of claim 10, wherein the first server is one of a plurality of distributed CDN servers, the first request is for a service accessible via the API, and the service comprises a service provided by the CDN.

13. The system of claim 10, wherein the first server is one of a plurality of distributed CDN servers, the first request is for a service accessible via the API, and the service enables interaction with any of:

(i) a multi-tenant storage system operated by the CDN on behalf of content providers, and (ii) a multi-tenant computing system operated by the CDN on behalf of content providers.

14. The system of claim 10, wherein the first server is one of a plurality of distributed CDN servers, the first request is for a service accessible via the API, and the service enables configuration by a CDN user of a CDN content delivery service, said configuration comprising configuration of CDN features and services for delivering any of a website and a web application being delivered on the CDN user'"'"'s behalf over the CDN.