URL rewriting pseudo proxy server

• US 5,835,718 A
• Filed: 04/10/1996
• Issued: 11/10/1998
• Est. Priority Date: 04/10/1996
• Status: Expired due to Term

• Current Assignee: Hanger Solutions, LLC (IP Investments Group LLC), Lucent Technologies, Inc. (Nokia Corporation)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Blewett, Charles Douglas
• Primary Examiner(s): Coleman, Eric
• Assistant Examiner(s): Monestime, Mackly
• Application Number:
  US08/631,720
• Time in Patent Office: 944 Days
• Field of Search: 395/200.01, 395/200.48, 395/200.49, 395/200.59, 395/200.33
• US Class Current: 709/218
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method for real time remapping of access to a selected remote domain in an interconnected computer system network comprising the steps defining a pseudo proxy server and translating in the pseudo proxy server a remote record identifier corresponding to the remote domain to a remapped record identifier corresponding to the local domain. In a further enhancement the method comprises the additional step of determining if a selected record identifier is a selected remapped record identifier.

Claims

1. In an interconnected computer system network a method of tracking and controlling access to remote record identifiers, said method comprising the steps of:

providing a first data set having a rewritten record identifier for a remote record identifier to a local user;

responding to a request from said local user for a selected record identifier;

determining if said selected record identifier is a rewritten record identifier;

determining an actual record identifier for said rewritten record identifier; and

requesting a second data set corresponding to said actual record identifier from said interconnected computer system network.

2. The method as recited in claim 1 wherein said first data set comprises a hypertext markup language based data set.

3. The method as recited in claim 1 wherein said remote record identifier comprises a uniform record locator.

4. The method as recited in claim 1 comprising the additional steps of determining that a record identifier is remote and rewriting said remote record identifier.

5. The method as recited in claim 4 wherein the steps of determining that a record identifier is remote comprises scanning a domain name of said actual record identifier and comparing said domain name to a local domain name wherein said record identifier is remote if said domain name is different than said local domain name.

6. The method as recited in claim 1 wherein the step of determining an actual record identifier for said rewritten record identifier comprises looking up said actual record identifier by a predetermined index.

7. The method as recited in claim 6 wherein the step of determining an actual record identifier further comprises a hashing table.

8. The method as recited in claim 7 wherein said hashing table comprises a minimal perfect hash.

9. The method as recited in claim 6 wherein the step of determining an actual record identifier further comprises addressing a memory location.

10. The method as recited in claim 6 wherein the step of determining an actual record identifier further comprises accessing an inode of a disk file.

11. The method as recited in claim 1 wherein the step of determining an actual record identifier for said rewritten record identifier comprises accessing a disk file by a file name.

12. The method as recited in claim 11 wherein said disk file contains a domain name of said actual record identifier.

13. The method as recited in claim 11 wherein said disk file contains said actual record identifier.

14. The method as recited in claim 1 wherein said request from said local user comprises a hypertext transfer protocol request.

15. In an interconnected computer system network a method of providing pseudo proxy access for tracking and controlling access to remote uniform record locators, said method comprising the steps of:

providing a hypertext markup language based page having a rewritten uniform record locator for a remote uniform record locator to a local user;

responding to a request from said local user for a selected uniform record locator;

determining if said selected uniform record locator is a rewritten uniform record locator;

determining an actual uniform record locator for said rewritten uniform record locator; and

requesting a second data set corresponding to said actual uniform record locator from said interconnected computer system network.

16. The method as recited in claim 15 comprising the additional steps of determining that a uniform record locator is remote by comparing a domain name of said uniform record locator to a local domain name, wherein said uniform record locator is remote if said domain name is different than said local domain name and rewriting said remote uniform record locator.

17. The method as recited in claim 15 wherein the step of determining an actual uniform record locator for said rewritten uniform record locator comprises looking up said actual uniform record locator by a predetermined index.

18. The method as recited in claim 17 wherein the step of determining an actual uniform record locator further comprises a hashing table.

19. The method as recited in claim 18 wherein said hashing table comprises a minimal perfect hash.

20. The method as recited in claim 15 wherein the step of determining an actual uniform record locator further comprises addressing a memory location.

21. The method as recited in claim 15 wherein the step of determining an actual uniform record locator further comprises accessing an inode of a disk file.

22. The method as recited in claim 15 wherein the step of determining an actual uniform record locator for said rewritten uniform record locator comprises accessing a disk file by a file name.

23. The method as recited in claim 15 comprising the additional steps of determining that a uniform record locator is remote by comparing a domain name of said uniform record locator to compared to a predetermined table of domain names and rewriting said remote uniform record locator.

24. In a computer server, a method of establishing a pseudo server, comprising the steps of:

receiving a request from a user,

fetching data requested by the user, said data containing pointers to secondary data,

identifying remote pointers, pointers that point to data remote from the computer server,

storing the remote pointers at the computer server,

generating rewritten pointers for the remote pointers, the rewritten pointers pointing to the corresponding stored remote pointers, and

transmitting the fetched data and rewritten pointers to the user.

25. The method of claim 24, wherein the rewritten pointers are blind pointers.

26. The method of claim 24, wherein the pointers are Uniform Resource Locators.

27. The method of claim 24, wherein the rewritten pointer references a disk file.

28. The method of claim 24, wherein the rewritten pointer references a location in memory.

29. The method of claim 24, wherein the user communicates with the computer server through the Internet.

30. The method of claim 24, wherein the user communicates with the computer server directly.

31. The method of claim 24, further comprising steps of:

receiving a request from the user, the request including a selected pointer,

determining whether the selected pointer is a rewritten pointer and, if so, retrieving the stored remote pointer corresponding to the selected pointer, and

retrieving data referenced by the retrieved remote pointer.

32. The method of claim 24, wherein the remote pointers are uniform resource locators.

33. The method of claim 24, wherein said generating step includes a step of looking up said remote record identifier by a predetermined index.

34. The method of claim 33, wherein said index is a hashing table.

35. The method of claim 34, wherein said hashing table includes a minimal perfect hash.

36. The method of claim 24, wherein said remote pointers are stored in a file by file name.

37. The method of claim 24, wherein said remote pointers are stored in a file by an inode.

38. The method of claim 24, wherein the request is a hypertext transfer protocol request.