Method of and system for analyzing the content of resource requests

• US 8,412,838 B1
• Filed: 10/26/2007
• Issued: 04/02/2013
• Est. Priority Date: 02/11/2002
• Status: Active Grant

• Current Assignee: Extreme Networks, Inc.
• Original Assignee: Extreme Networks, Inc.
• Inventors: Wang, Wei, TRAN, KIET, Lowe, Ricky K., Liu, Liang, Gomez, Miguel
• Primary Examiner(s): Dalencourt, Yves
• Assistant Examiner(s): Lai, Michael C
• Application Number:
  US11/925,621
• Time in Patent Office: 1,985 Days
• Field of Search: 709/229, 709/227, 709/225, 713/153, 726/5
• US Class Current: 709/229
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: H04L 12/00 Data switching networks interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units G06F13/00
• CPC Class Codes: H04L 12/6418 Hybrid transport
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 45/7453 using hashing
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/805 QOS or priority aware
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Systems and methods are described for analyzing the content of resource requests. A tokenizer parses the resource request and derives a key therefrom. A database associates values of the key with categories of service. An association engine uses the key to obtain one or more matching entries from the database, and derive therefrom the desired category of service for the resource request. A cookie engine derives cookie information from a cookie located in the resource request. A session engine derives session information from a session identifier located in a handshake message associated with the resource request. The desired category of service, the cookie information, and the session information are each useful for allocating a resource to the resource request.

Claims

1. A method of processing a resource request performed by or for a processor, the method comprising:

obtaining a predetermined cookie name responsive to an unencrypted resource request via an indicator of a desired class of service for the unencrypted resource request as a key to access a content addressable memory (CAM) database associating values of the key with predetermined cookie names, resulting in a matching database entry;

obtaining cookie information from a cookie value associated with a cookie in response to determining that the predetermined cookie name is present in the unencrypted resource request, wherein the cookie is an item of state-related information for insertion into an http object, wherein the cookie information represents a cookie identifier useful for identifying whether a connection exists or recently expired between a client which issued the resource request and a server which originated the cookie;

providing, as cookie information, a default cookie identifier in response to determining that the predetermined cookie name is absent in the unencrypted resource request;

obtaining a session identifier from a handshake message relating to the resource request in response to determining that the resource request is an encrypted resource request; and

obtaining session information from the session identifier corresponding to the encrypted resource request.

2. The method of claim 1, wherein the step of determining whether a cookie having the predetermined name is present in the resource request comprises searching through multiple cookie headers or attributes located in the resource request.

3. The method of claim 1, wherein the session identifier is a Secure Sockets Layer (SSL) session ID string.

4. The method of claim 1, wherein the resource request is embodied as a http header.

5. The method of claim 1, wherein the resource request is embodied as a https header.

6. The method of claim 1, wherein obtaining cookie information comprises extracting the cookie information via a cookie engine.

7. The method of claim 6, wherein obtaining the session identifier from the handshake message comprises obtaining the session identifier via a session engine coupled to the cookie engine.

8. The method of claim 1, wherein obtaining the cookie information further comprises processing the cookie value according to a cookie processing mode associated with the cookie value.

9. The method of claim 8, wherein the cookie processing mode comprises one of:

a self-identification mode;

a directive hash model;

or

a cookie learning mode.

10. The method of claim 9, wherein the cookie value associated with the self-identification mode is an IP or Media Access Control (MAC) address of a server.

11. The method of claim 9, wherein in the directive hash mode, a hash function is applied to the cookie value in response to matching the predetermined cookie name.

12. The method of claim 9, wherein in the cookie learning mode, a cookie identifier is derived from the cookie value in response to matching the predetermined cookie name.

13. The method of claim 1, wherein the key is derived from a combination of a Base Service Index (BSI) and a server Internet Protocol (IP) address.

14. The method of claim 1, wherein an entry in the CAM database associates a key comprising one of:

a Base Service Index (BSI), or

a Uniform Resource Locator (URL) path combination with a Content Analyzer Service Index (CSI).

15. The method of claim 14, wherein the entry in the CAM database includes a command specifying a type of match for the key.

16. The method of claim 14, wherein the entry in the CAM database includes an action to be taken when a specified type of match for the key is detected.

22. The method of any one of claim 1 or 17, wherein the cookie value is a server address, and the cookie information is a combination of the indicator of the desired class of service for the resource request and the server address.

23. The method of any one of claim 1 or 17, wherein the cookie information is a hash value that results when a hash function is applied to the cookie value.

24. The method of any one of claim 1 or 17, wherein the cookie information is a combination of an indicator of a desired sub-class of service for the resource request and a hash value that results when a hash function is applied to the cookie value.

25. The method of any one of claim 1 or 17, wherein the session information is a hash value that results when a hash function is applied to the session identifier.

26. The method of any one of claim 1 or 17, wherein the cookie value is a server identifier.

27. The method of claim 26, wherein the cookie information is the server identifier.

28. The method of any one of claim 1 or 17, wherein the cookie value is mapped to a server identifier via a mapping table.

29. The method of any one of claim 1 or 17, wherein the database is a cookie name table.

17. A method, performed in, by or for a processor, of determining cookie information from an analysis of content of a resource request, the method comprising:

accessing a content addressable memory (CAM) database associating values of a key with a cookie processing mode via an indicator of a desired class of service for the resource request as the key to accessing the CAM database;

obtaining a matching database entry from the accessed CAM database associating values of the key; and

determining the cookie processing mode for the request from the matching entry;

locating a cookie in the resource request, wherein the cookie is an item of state-related information for insertion into an http object; and

processing a cookie value for the cookie in accordance with the determined cookie processing mode to obtain the cookie information, wherein the cookie information represents a cookie identifier useful for identifying whether a connection exists or recently expired between a client which issued the resource request and a server which originated the cookie.

18. The method of claim 17, wherein the cookie information is a service identifier useful for identifying a server through a hierarchical arrangement of data structures.

19. The method of claim 17, wherein the cookie information is a default cookie identifier.

20. The method of claim 19, wherein the default cookie identifier is provided upon or after a determination that a cookie having a specified name is not present in the resource request.

21. The method of claim 19, wherein the default cookie identifier is provided upon or after a determination that a server identifier is not obtainable from the value of a cookie located in the resource request.

30. A system for processing a resource request comprising:

a content addressable memory (CAM) database for associating cookie names with resource requests, and for further associating cookie names with a desired class of service for the resource requests;

a cookie engine configured to;

access the CAM database to identify an entry in the CAM database matching a desired class of service for the resource request via an indicator of the desired class of service for the resource request as a key to accessing the CAM database, wherein the resource request being an unencrypted resource request,

determine a cookie name associated with the unencrypted resource request,

locate a cookie in the unencrypted resource request with the cookie name, wherein the cookie is an item of state-related information for insertion into an http object, and

obtain the cookie information from a cookie value associated with the cookie in the unencrypted resource request, wherein the cookie information represents a cookie identifier useful for identifying whether a connection exists or recently expired between a client which issued the resource request and a server which originated the cookie; and

a session engine coupled with the cookie engine and configured to;

obtain a session identifier from a handshake message associated with a resource request, the resource request being an encrypted resource request, and

obtain the session information from the session identifier associated with the encrypted resource request.

31. The system of claim 30, wherein the cookie engine is further configured to provide a default cookie identifier if a cookie having the name associated with the resource request is not present in the resource request.

32. The system of claim 30, wherein the cookie engine is further configured to search through multiple cookie headers or attributes in the resource request to locate a cookie having the name associated with the resource request.

33. The system of claim 30, wherein the cookie information identifies the server which issued the cookie.

34. The system of claim 30, wherein the cookie information identifies a current or recently expired connection with the server which issued the cookie.

35. The system of claim 30, wherein the cookie information is useful for locating the service which issued the cookie through a hierarchical arrangement of data structures.

36. The system of claim 30, wherein the session identifier is a Secure Sockets Layer (SSL) session ID string.

37. The system of claim 30, wherein the session identifier identifies a current or recently expired connection with the server which issued the session identifier.

38. The system of claim 30, wherein the resource request is embodied as a http or https header.

40. The system of any one of claim 30 or 39, wherein the cookie value is a server address, and the cookie information is a combination of an indicator of the desired class of service for the resource request and the server address.

41. The system of any one of claim 30 or 39, wherein the cookie information is a hash value that results when a hash function is applied to the cookie value.

42. The system of any one of claim 30 or 39, wherein the cookie information is a combination of an indicator of a desired sub-class of service for the resource request and a hash value that results when a hash function is applied to the cookie value.

43. The system of any one of claim 30 or 39, wherein the session information is a hash value that results when a hash function is applied to the session identifier.

44. The system of any one of claim 30 or 39, wherein the cookie value is a server identifier.

45. The system of any one of claim 30 or 39, wherein the cookie information is the server identifier.

46. The system of any one of claim 30 or 39, wherein the cookie value is mapped to a server identifier via a mapping table.

47. The system of any one of claim 30 or 39, wherein the database is a cookie name table.

39. A system for obtaining cookie information from a resource request comprising:

a content addressable memory (CAM) database associating cookie processing modes with desired classes of service for resource requests; and

a cookie engine for accessing the database to identify an entry in the CAM database matching a desired class of service for the resource request via an indicator of the desired class of service for the resource request as a key to accessing the CAM database, and for determining therefrom a cookie processing mode associated with the resource request, locating a cookie within the resource request, and processing a cookie value for the cookie in accordance with the cookie processing mode to obtain the cookie information, wherein the cookie is an item of state-related information for insertion into an http object, and

wherein the cookie information represents a cookie identifier useful for identifying whether a connection exists or recently expired between a client which issued the resource request and a server which originated the cookie.