Scheme for segregating cacheable and non-cacheable by port designation

• US 6,587,928 B1
• Filed: 02/28/2000
• Issued: 07/01/2003
• Est. Priority Date: 02/28/2000
• Status: Expired due to Term

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: Blue Coat Systems Incorporated (Gen Digital Inc.)
• Inventors: Kellner, Michael D., Periyannan, Alagu S.
• Primary Examiner(s): NGUYEN, THAN VINH
• Application Number:
  US09/515,069
• Time in Patent Office: 1,219 Days
• Field of Search: 711/118,130,133,138,139,131 709/245,219
• US Class Current: 711/138
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Requests are identified as being for a cacheable object or a non-cacheable object according to information included in a Uniform Resource Locator (URL) associated with the object. For example, the URL may include a port designation for requests for cacheable objects (e.g., images and the like). Thus, a request may be recognized as being for a cacheable or non-cacheable object according to the port on which the request is made. In some cases, requests for non-cacheable objects may be made on port 80. A router may be thus configured to recognize a request as being for a cacheable object or a non-cacheable object according to a port on which the request is received and redirect it to a cache as appropriate.

Claims

1. A computer-implemented process comprising recognizing a request as being for a cacheable object or a non-cacheable object according to information included in a Uniform Resource Locator (URL) associated with the object, wherein the URL includes an explicit port designation other than port 80 when the request is for a cacheable object.

2. The process of claim 1 wherein the request is recognized as being for a cacheable or non-cacheable object according to a port designation included in the URL.

3. The process of claim 2 wherein the request is recognized as being for a non-cacheable object when the request is made on port 80.

4. The process of claim 2 wherein the request is recognized as being for a cacheable object when the request is not made on port 80.

9. The process of claim 1 further comprising directing the request to bypass a cache when the request is for a non-cacheable object.

5. A system comprising

a router configured to recognize a request as being for a cacheable object or a non-cacheable object according to a port on which the request is received.

10. The system of claim 5, wherein the router is further configured to direct the request to a cache coupled to the router when the port on which the request is received is different from port 80.

11. The system of claim 10, wherein the router is further configured to direct the request to a server when the object is not located in the cache, wherein the object is stored in the cache after being retrieved from the server.

12. The system of claim 5, wherein the router is further configured to direct the request to a server when the port on which the request is received is port 80.

6. A method comprising configuring a Uniform Resource Locator (URL) to identify when an object associated with the URL the object is cacheable when the port designation in the URL is other than port 80 is to be cached by including a port designation information in the URL.

7. The method of claim 6 wherein the object is to be cached when the port designation in the URL is different from port 80.

13. The method of claim 6, wherein the object is to be cached when the port designation information in the URL indicates a port other than port 80.

8. A method comprising redirecting a request from a client communicatively coupled to a network to a resource also coupled to the network according to whether the request is for a cacheable object as determined by a port designation other than port 80 included within a Uniform Resource Location (URL) associated with the object.

14. A computer readable medium having stored thereon sequences of instructions which are executable by a system, and which, when executed by the system, cause the system to perform a method, comprising:

recognizing a request as being for a cacheable object or a non-cacheable object according to a port designation other than port 80 included in a Uniform Resource Locator (URL) associated with the object.

15. The computer medium of claim 14, wherein the request is recognized as being for a cacheable object when the URL includes an explicit port designation other than port 80.

16. The computer medium of claim 15, wherein the request is recognized as being for a non-cacheable object when the URL includes an explicit port designation of port 80.