REWRITTEN URL STATIC AND DYNAMIC CONTENT DELIVERY

• US 20100332588A1
• Filed: 06/30/2009
• Published: 12/30/2010
• Est. Priority Date: 06/30/2009
• Status: Active Grant

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Group Incorporated (GoDaddy, Inc.)
• Inventors: Schwimer, Greg
• Granted Patent: US 8,078,757 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• 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/1021 based on client or server locations
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Systems and methods of the present invention provide for returning website content after being requested by a client. A dynamic component and a rewritten URL may be requested and a static component may be requested, which may be updated. The combination of static and dynamic website content may be returned to the client.

Claims

1. A method comprising:

a) receiving, by a router communicatively coupled to a computer network, a request for a website content from a client, said website content comprising a dynamic component and a static component;

b) identifying, by said router, a data center in closest physical proximity to said client, said data center comprising one in a plurality of data centers;

c) requesting from a shared hosting server in said data center, by said client, said dynamic component and a rewritten URL for requesting said static component;

d) locating, using said rewritten URL, said static component within a cache server in said data center;

e) requesting, by said cache server, an update to said static component from said shared hosting server; and

f) returning, by said cache server, said website content to said client.

2. The method of claim 1 wherein said network is a content delivery network.

3. The method of claim 1 wherein said shared hosting server comprises an edge server wherein said edge server establishes said data center as a regional distribution point based on physical proximity to said client.

4. The method of claim 1 wherein said shared hosting server comprises an origin server.

5. The method of claim 4 further comprising the step of offloading, by said origin server, the delivery of static content, by redirecting to said client, then to said cache server, using said rewritten URL.

6. The method of claim 4 further comprising the step of identifying said dynamic component to be fetched from said origin server.

7. The method of claim 1 wherein said dynamic component is determined to be incapable of being cached.

8. The method of claim 4 further comprising the step of locating in a database, by said origin server, a stored content used in said dynamic component, wherein said stored content is located in a storage subsystem communicatively coupled to said origin server.

9. The method of claim 8 further comprising the step of processing, by said origin server, said stored content, wherein said processing comprises:

i) analyzing said stored content; and

ii) determining whether and which said stored content should be displayed as part of said dynamic content.

10. The method of claim 1 further comprising the step of processing a requested SSL certificate.

11. The method of claim 9 further comprising the step of returning said dynamic component, plus re-written URLs for static content, to said client after processing said stored content.

12. The method of claim 1 wherein said static component comprises streaming content.

13. The method of claim 1 wherein said cache server comprises additional caching layers.

14. The method of claim 1 further comprising the step of determining, by said cache server, whether said static component is contained within a local cache repository communicatively coupled to said cache server.

15. The method of claim 4 further comprising the step of requesting, by said cache server, updates to said static component via a header request for a cacheable content to said origin server.

16. The method of claim 4 further comprising the step of determining, by said origin server, updates required for said static component.

17. The method of claim 14 further comprising the step of updating said local cache repository with said cacheable content.

18. A system, comprising:

a) a client communicatively coupled to a computer network, said website content comprising a dynamic component and a static component;

b) a router communicatively coupled to said computer network for receiving a request for said website content from said client;

c) a plurality of data centers communicatively coupled to said computer network having one data center in closest physical proximity to said client;

d) a shared hosting server hosted in said data center, said shared hosting server receiving a request from said client for said dynamic component, a rewritten URL to locate and retrieve said static component, and an HTTP redirect to locate and update said static component; and

e) a cache server hosted in said data center used to locate, using said rewritten URL, said static component within said cache server and which returns said website content to said client, wherein said cache server is not said shared hosting server.