Methods and apparatus for redirecting network cache traffic

• US 6,532,493 B1
• Filed: 10/29/1998
• Issued: 03/11/2003
• Est. Priority Date: 10/29/1998
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Cieslak, Martin K., Kagan, Martin A., Aviani, James A. Jr.
• Primary Examiner(s): Sheikh, Ayaz
• Assistant Examiner(s): DINH, KHANH Q
• Application Number:
  US09/183,600
• Time in Patent Office: 1,594 Days
• Field of Search: 709/220, 709/221, 709/200, 709/224, 709/245, 709/228, 370/94.1, 370/400, 370/397, 370/395
• US Class Current: 709/224
• CPC Class Codes: H04L 67/2885 Hierarchically arranged intermediate devices, e.g. for hierarchical caching
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method for routing a data request received by a caching system is described. The caching system includes a router and a cache, and the data request identifies a source platform, a destination platform, and requested data. Where the source and destination platforms correspond to an entry in a list automatically generated by the caching system, the data request is transmitted without determining whether the requested data are stored in the cache.

Claims

1. A method for routing a data request received by a caching system comprising a router and a cache, the data request identifying a source platform, a destination platform, and requested data, the method comprising, where a first identifier associated with the source platform and a second identifier associated with the destination platform are contained in an entry in a list automatically generated by the caching system, transmitting the data request without determining whether the requested data are stored in the cache, wherein the list is automatically generated according to a method comprising:

receiving a first transmission corresponding to the data request;

determining that the requested data are not in the cache;

attempting to establish a connection between the cache and the destination platform; and

in response to receiving notification that the connection has failed, automatically storing the entry in the list.

2. The method of claim 1 wherein each entry in the list corresponds to a destination platform for which user authentication is required.

3. The method of claim 1 wherein each entry in the list corresponds to a source platform for which special processing of the requested data is required.

4. The method of claim 1 wherein notification that the connection has failed comprises a 401 response in an HTTP header associated with the data request.

5. The method of claim 1 wherein notification that the connection has failed comprises a 403 response in an HTTP header associated with the data request.

6. The method of claim 1 wherein transmitting the data request comprises:

prompting the source platform to retransmit the data request; and

in response to the entry in the list, passing the retransmitted data request through the caching system without determining whether the requested data are stored in the cache.

7. The method of claim 6 wherein prompting the source platform to retransmit the data request comprises transmitting a 302 response to the source platform in an HTTP header associated with the data request.

8. The method of claim 1 wherein the list resides in the cache.

9. The method of claim 1 wherein the list resides in the router.

10. The method of claim 9 wherein the header comprises an HTTP header.

11. The method of claim 1 wherein transmitting the data request comprises attempting to establish a connection between the cache and the destination platform, the attempted connection identifying the source and destination platforms to upstream caching systems.

12. The method of claim 11 wherein identification of the source and destination platforms to upstream caching systems comprises a modification to a header associated with the data request which identifies the source platform regardless of subsequent encapsulation.

13. The method of claim 1 wherein the list is automatically generated according to a method comprising, where a data field in a header associated with the data request corresponds to a second entry in a second list associated with caching system, automatically storing the entry in the list.

14. The method of claim 13 wherein the header comprises an HTTP header.

15. The method of claim 13 wherein the data field indicates whether the source platform requires special processing of the requested data.

16. The method of claim 13 wherein the second list comprises a plurality of entries each corresponding to a type of platform for which special processing of transmitted content is required.

17. The method of claim 16 wherein each of the plurality of entries in the second list also corresponds to third party software which provides the special processing required by the corresponding type of platform.

18. The method of claim 17 wherein the third party software comprises HTML munging software.

19. The method of claim 17 wherein the third party software comprises XML processing software.

20. The method of claim 17 wherein the third party software comprises image distillation software.

21. The method of claim 17 wherein the third party software comprises multi-language support software.

22. The method of claim 16 wherein the second list resides in the cache.

23. The method of claim 16 wherein the second list resides in the router.

24. The method of claim 13 wherein transmitting the data request comprises, in response to the entry in the list, diverting the data request to a third party platform corresponding to the second entry in the second list.

25. A method for routing a first data request received by a caching system comprising a router and a cache, the data request identifying a source platform, a destination platform, and requested data, the method comprising:

determining that the requested data are not in the cache;

attempting to establish a connection between the cache and the destination platform;

in response to receiving notification that the connection has failed, automatically storing an entry containing information identifying the source platform and information identifying the destination platform in a list generated by the caching system;

prompting the source platform to transmit a second data request for the requested data, the second data request identifying the source and destination platforms; and

in response to the entry in the list, passing the second data request through the caching system without determining whether the requested data are stored in the cache.

26. A method for routing a data request received by a caching system comprising a router and a cache, the method comprising:

identifying a source platform in the data request;

identifying a destination platform in the data request;

determining that the source platform and the destination platform are associated in a data structure automatically generated by the caching system;

transmitting the data request without determining whether the requested data are stored in the cache;

wherein the data structure is automatically generated according to a method comprising;

receiving a first transmission corresponding to the data request;

determining that the requested data are not in the cache;

attempting to establish a connection between the cache and the destination platform; and

in response to receiving notification that the connection has failed, automatically storing the entry in the data structure.

27. The method of claim 26 wherein each entry in the data structure corresponds to a destination platform for which user authentication is required.

28. The method of claim 26 wherein each entry in the data structure corresponds to a source platform for which special processing of the requested data is required.

29. The method of claim 26 wherein notification that the connection has failed comprises a 401 response in an HTTP header associated with the data request.

30. The method of claim 26 wherein notification that the connection has failed comprises a 403 response in an HTTP header associated with the data request.

31. The method of claim 26 wherein transmitting the data request comprises:

prompting the source platform to retransmit the data request; and

in response to the entry in the data structure, passing the retransmitted data request through the caching system without determining whether the requested data are stored in the cache.

32. The method of claim 31 wherein prompting the source platform to retransmit the data request comprises transmitting a 302 response to the source platform in an HTTP header associated with the data request.

33. The method of claim 26 wherein the data structure is a bypass list.

34. A caching system having a router and a cache for routing a data request, the caching system comprising:

means for identifying a source platform in the data request;

means for identifying a destination platform in the data request;

means for determining that the source platform and the destination platform are associated in a data structure automatically generated by the caching system;

means for transmitting the data request without determining whether the requested data are stored in the cache;

wherein the data structure is automatically generated according to a caching system comprising;

means for receiving a first transmission corresponding to the data request;

means for determining that the requested data are not in the cache;

means for attempting to establish a connection between the cache and the destination platform;

means for receiving notification that the connection has failed; and

means for automatically storing the entry in the data structure.

35. The caching system of claim 34 wherein each entry in the data structure corresponds to a destination platform for which user authentication is required.

36. The caching system of claim 34 wherein each entry in the data structure corresponds to a source platform for which special processing of the requested data is required.

37. The caching system of claim 34 wherein notification that the connection has failed comprises a 401 response in an HTTP header associated with the data request.

38. The caching system of claim 34 wherein notification that the connection has failed comprises a 403 response in an HTTP header associated with the data request.

39. The caching system of claim 34 wherein means for transmitting the data request comprises:

means for prompting the source platform to retransmit the data request;

means for identifying the entry in the data structure; and

means for passing the retransmitted data request through the caching system without determining whether the requested data are stored in the cache.

40. The caching system of claim 39 wherein prompting the source platform to retransmit the data request comprises transmitting a 302 response to the source platform in an HTTP header associated with the data request.

41. The caching system of claim 34 wherein the data structure is a bypass list.

42. A computer readable medium comprising computer code for routing a data request at a caching system, the computer code comprising:

computer code for identifying a source platform in the data request;

computer code for identifying a destination platform in the data request;

computer code for determining that the source platform and the destination platform are associated in a data structure automatically generated by the caching system;

computer code for transmitting the data request without determining whether the requested data are stored in the cache;

wherein computer code for automatically generating the data structure comprises;

computer code for receiving a first transmission corresponding to the data request;

computer code for determining that the requested data are not in the cache;

computer code for attempting to establish a connection between the cache and the destination platform;

computer code for receiving notification that the connection has failed; and

computer code for automatically storing the entry in the data structure.

43. The computer readable medium of claim 42 wherein each entry in the data structure corresponds to a destination platform for which user authentication is required.

44. The computer readable medium of claim 42 wherein each entry in the data structure corresponds to a source platform for which special processing of the requested data is required.

45. The computer readable medium of claim 42 wherein notification that the connection has failed comprises a 401 response in an HTTP header associated with the data request.

46. The computer readable medium of claim 42 wherein notification that the connection has failed comprises a 403 response in an HTTP header associated with the data request.

47. The computer readable medium of claim 42 wherein computer code for transmitting the data request comprises:

computer code for prompting the source platform to retransmit the data request;

computer code for identify the entry in the data structure, and

computer code for passing the retransmitted data request through the caching system without determining whether the requested data are stored in the cache.

48. The computer readable medium of claim 47 wherein prompting the source platform to retransmit the data request comprises transmitting a 302 response to the source platform in an HTTP header associated with the data request.

49. The computer readable medium of claim 42 wherein the data structure is a bypass list.