Generation of unique significant key from URL get/post content

• US 7,987,509 B2
• Filed: 11/10/2005
• Issued: 07/26/2011
• Est. Priority Date: 11/10/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Martin, Sean J., Martin, Simon L., Torres, Elias, Feigenbaum, Lee
• Primary Examiner(s): Parthasarathy; Pramila
• Application Number:
  US11/272,338
• Publication Number:
  US 20070104326A1
• Time in Patent Office: 2,084 Days
• Field of Search: 380/44, 713/189, 726/2, 726/22
• US Class Current: 726/26
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 63/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08

Abstract

Generating a unique URL key for a web document according to an obtained key generating policy. The URL of a web page is parsed according to the policy in order to generate the URL key. Preferably, the key generating policy is obtained from a well known source associated with the web page.

Claims

1. A computer implemented method for generating canonicalized keys, the method comprising:

receiving by the computer, a request from a requestor for a canonicalized key, the request comprising a first uniform resource address (URA) for locating a corresponding web page, the first URA comprising an authority and a query string of query parameters, the first URA consisting of any one of a uniform resource identifier (URI) or a uniform resource locator (URL);

obtaining by the computer, a key generating policy for generating the canonicalized key;

transforming the query string by the computer to produce a transformed query string based on said obtained key generating policy, wherein the transforming consists of reordering the query parameters, removing query parameters or adding query parameters; and

generating by the computer, the canonicalized key based on the transformed query string, wherein the generated canonicalized key comprises a second URA comprising the authority and the transformed query string.

2. The method according to claim 1, wherein the obtained key generating policy causes the creating the transformed query string step to perform one or more steps consisting of any one of:

selectively positioning one or more of said query parameters of the first URA in the second URA,

selectively not including one or more query parameters of the first URA in the second URA,

including an HTTP header in the canonicalized key,

selectively adding one or more additional query parameters to the second URA, wherein the one or more additional query parameters consist of query parameters not included in the first URA,

selectively including POST query data in the canonicalized key,

selectively including HTTP basic authentication information in the canonicalized key, and

prompting a user for the additional information for generating the canonicalized key.

3. The method according to claim 1, further comprising:

associating the canonicalized key with external data; and

using the canonicalized key to obtain external data to provide to the requestor a version of the web document as it existed when the canonicalized key was associated with the external data.

4. The method according to claim 1, wherein the key generating policy comprises any one of a policy related to a user or a policy provided by a web service.

5. The method according to claim 1, wherein the first query string comprises first parameters absent in the second URA.

6. The method according to claim 1, further comprising using the canonicalized key to search a cache for the corresponding web page.

7. The method according to claim 6, further comprising:

responsive to determining the generated canonical key is not in the cache performing a) though c);

a) retrieving the web page associated with the first URA,

b) associating the generated canonicalized key with the retrieved web page; and

c) saving the retrieved web page and associated generated canonicalized key in the cache; and

responsive to determining the generated canonicalized key is in the cache, retrieving the web page associated with the canonicalized key from the cache.

8. A computer program product for generating canonicalized keys, the computer program product comprising:

receiving by the computer, a request from a requestor for a canonicalized key, the request comprising a first uniform resource address (URA) for locating a corresponding web page, the first URA comprising an authority and a query string of query parameters, the first URA consisting of any one of a uniform resource identifier (URI) or a uniform resource locator (URL);

obtaining by the computer, a key generating policy for generating the canonicalized key;

transforming the query string by the computer to produce a transformed query string based on said obtained key generating policy, wherein the transforming consists of reordering the query parameters, removing query parameters or adding query parameters; and

generating by the computer, the canonicalized key based on the transformed query string, wherein the generated canonicalized key comprises a second URA comprising the authority and the transformed query string comprising the first authority and the second query string.

9. The computer program product according to claim 8, wherein the obtained key generating policy causes the creating the transformed query string step to perform one or more steps consisting of any one of:

selectively positioning one or more of said query parameters of the first URA in the second URA,

selectively not including one or more query parameters of the first URA in the second URA,

including an HTTP header in the canonicalized key,

selectively adding one or more additional query parameters to the second URA, wherein the one or more additional query parameters consist of query parameters not included in the first URA,

selectively including POST query data in the canonicalized key,

selectively including HTTP basic authentication information in the canonicalized key, and

prompting a user for the additional information for generating the canonicalized key.

10. The computer program product according to claim 8, wherein the first query string comprises first parameters absent in the second URA.

11. The computer program product according to claim 8, further comprising using the canonicalized key to search a cache for the corresponding web page.

12. The computer program product according to claim 11, further comprising:

responsive to determining the generated canonical key is not in the cache performing a) though c);

a) retrieving the web page associated with the first URA,

b) associating the generated canonicalized key with the retrieved web page; and

c) saving the retrieved web page and associated generated canonicalized key in the cache; and

responsive to determining the generated canonicalized key is in the cache, retrieving the web page associated with the canonicalized key from the cache.

13. A system for generating canonicalized keys, the system comprising:

a network;

a server system in communication with the network

a client system in communication with the server system wherein the system includes instructions to execute a method comprising the steps of;

receiving by the computer, a request from a requestor for a canonicalized key, the request comprising a first uniform resource address (URA) for locating a corresponding web page, the first URA comprising an authority and a query string of query parameters, the first URA consisting of any one of a uniform resource identifier (URI) or a uniform resource locator (URL);

obtaining by the computer, a key generating policy for generating the canonicalized key;

transforming the query string by the computer to produce a transformed query string based on said obtained key generating policy, wherein the transforming consists of reordering the query parameters, removing query parameters or adding query parameters; and

generating by the computer, the canonicalized key based on the transformed query string, wherein the generated canonicalized key comprises a second URA comprising the authority and the transformed query string.

14. The system according to claim 13, wherein the obtained key generating policy causes the creating the transformed query string step to perform one or more steps consisting of any one of:

selectively positioning one or more of said query parameters of the first URA in the second URA,

selectively not including one or more query parameters of the first URA in the second URA,

including an HTTP header in the canonicalized key,

selectively adding one or more additional query parameters to the second URA, wherein the one or more additional query parameters consist of query parameters not included in the first URA,

selectively including POST query data in the canonicalized key,

selectively including HTTP basic authentication information in the canonicalized key, and

prompting a user for the additional information for generating the canonicalized key.

15. The method according to claim 13, wherein the first query string comprises first parameters absent in the second URA.

16. The system according to claim 13, further comprising using the canonicalized key to search a cache for the corresponding web page.

17. The system according to claim 16, further comprising the further steps of:

responsive to determining the generated canonical key is not in the cache performing a) though c);

a) retrieving the web page associated with the first URA,

b) associating the generated canonicalized key with the retrieved web page; and

c) saving the retrieved web page and associated generated canonicalized key in the cache; and

responsive to determining the generated canonicalized key is in the cache, retrieving the web page associated with the canonicalized key from the cache.

18. The system according to claim 13, further comprising:

associating the canonicalized key with external data; and

using the canonicalized key to obtain external data to provide to the requestor a version of the web document as it existed when the canonicalized key was associated with the external data.