Generation of unique significant key from URL get/post content

• US 20070104326A1
• Filed: 11/10/2005
• Published: 05/10/2007
• Est. Priority Date: 11/10/2005
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Torres, Elias, Feigenbaum, Lee, Martin, Simon, Martin, Sean
• Granted Patent: US 7,987,509 B2
• Time in Patent Office: Days
• US Class Current: 380/44
• 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 unique internet uniform resource keys, the method comprising:

receiving a request for a web document, the request comprising a uniform resource address (URA), the URA comprising of any one of a uniform resource identifier (URI) or a uniform resource locator (URL);

obtaining a key generating policy;

generating a unique URA key based on the obtained key generating policy and the URA.

2. The method according to claim 1 wherein the key generating policy comprise of any one of:

including information,

excluding the information, or

transforming the information;

wherein the information comprises any one of;

the URA,

HTTP request headers, or

HTTP request data.

3. The method according to claim 2, wherein the transforming the information step comprises any one of the further steps consisting of:

looking-up a DNS CNAME,

reordering query parameters,

removing one or more query parameters,

including HTTP headers,

adding additional query parameters,

including POST request data,

including http basic authentication information, or

prompting a user for the additional information.

4. The method according to claim 1 comprising the further steps of:

retrieving components of a page associated with the URA;

associating the generated URA key with the retrieved components;

saving the retrieved components and associated generated URA key in a cache.

5. The method according to claim 1 comprising the further steps of:

receiving a request for the web document; and

retrieving the saved retrieved components and associated generated URA from the cache.

6. The method according to claim 1, comprising the further step of associating the unique URA key with external data.

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

receiving a request to provide the web document; and

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

8. The method according to claim 1, wherein the policy comprises any one of a policy related to the URA, a policy related to a user, a policy provided by a web service, a policy independent of the URA or a policy independent of any URA.

9. The method according to claim 1 wherein the obtaining the key generating policy comprises any one of the further steps consisting of:

receiving the policy from an application program;

fetching the policy from a well-known public policy repository;

fetching the policy from a queryable server;

fetching the policy from a well-known location relative to the host machine hosting the web document being served;

or

fetching the policy from a well-known location relative to the root of the host machine hosting the web document being served.

10. A computer program product for generating unique internet uniform resource keys, the computer program product comprising:

a storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising;

receiving a request for a web document, the request comprising a uniform resource address (URA), the URA comprising of any one of a uniform resource identifier (URI) or a uniform resource locator (URL);

obtaining a key generating policy;

generating a unique URA key based on the obtained key generating policy and the URA.

11. The computer program product according to claim 10 wherein the key generating policy comprise of any one of:

including information,

excluding the information, or

transforming the information;

wherein the information comprises any one of;

the URA,

HTTP request headers, or

HTTP request data.

12. The computer program product according to claim 11, wherein the transforming the information step comprises any one of the further steps consisting of:

looking-up a DNS CNAME,

reordering query parameters,

removing one or more query parameters,

including HTTP headers,

adding additional query parameters,

including POST request data,

including http basic authentication information, or

prompting a user for the additional information.

13. The computer program product according to claim 10 comprising the further steps of:

retrieving components of a page associated with the URA;

associating the generated URA key with the retrieved components;

saving the retrieved components and associated generated URA key in a cache.

14. The computer program product according to claim 10 comprising the further steps of:

receiving a request for the web document; and

retrieving the saved retrieved components and associated generated URA from the cache.

15. The computer program product according to claim 10 wherein the obtaining the key generating policy comprises any one of the further steps consisting of:

receiving the policy from an application program;

fetching the policy from a well-known public policy repository;

fetching the policy from a queryable server;

fetching the policy from a well-known location relative to the host machine hosting the web document being served;

or

fetching the policy from a well-known location relative to the root of the host machine hosting the web document being served.

16. A system for generating unique internet uniform resource 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 a request for a web document, the request comprising a uniform resource address (URA), the URA comprising of any one of a uniform resource identifier (URI) or a uniform resource locator (URL);

obtaining a key generating policy;

generating a unique URA key based on the obtained key generating policy and the URA.

17. The system according to claim 16 wherein the key generating policy comprise of any one of:

including information,

excluding the information, or

transforming the information;

wherein the information comprises any one of;

the URA,

HTTP request headers, or

HTTP request data.

18. The system according to claim 17, wherein the transforming the information step comprises any one of the further steps consisting of:

looking-up a DNS CNAME,

reordering query parameters,

removing one or more query parameters,

including HTTP headers,

adding additional query parameters,

including POST request data,

including http basic authentication information, or

prompting a user for the additional information.

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

retrieving components of a page associated with the URA;

associating the generated URA key with the retrieved components;

saving the retrieved components and associated generated URA key in a cache.

20. The system according to claim 16, wherein the obtaining the key generating policy comprises any one of the further steps consisting of:

receiving the policy from an application program;

fetching the policy from a well-known public policy repository;

fetching the policy from a queryable server;

fetching the policy from a well-known location relative to the host machine hosting the web document being served;

or

fetching the policy from a well-known location relative to the root of the host machine hosting the web document being served.