System and method of mediating a web page

• US 7,631,102 B2
• Filed: 07/25/2005
• Issued: 12/08/2009
• Est. Priority Date: 11/12/1999
• Status: Expired due to Term

• Current Assignee: BMC Software Incorporated (KKR & Co., Inc.)
• Original Assignee: BMC Software Incorporated (KKR & Co., Inc.)
• Inventors: Davis, Clay, Klobe, Michael C., Bodwell, Walter R.
• Primary Examiner(s): LAZARO, DAVID R
• Application Number:
  US11/189,057
• Publication Number:
  US 20050256955A1
• Time in Patent Office: 1,597 Days
• Field of Search: 709/203, 709217-219, 709/224, 709/226, 709/246
• US Class Current: 709/246
• CPC Class Codes: G06F 16/986 Document structures and storage, e.g. HTML extensions

Abstract

A system and method for mediating a web page at an intermediate server. The system and method can include receiving a web page from a target web server, ensuring that the web page is not cached and changing links in the web page to refer to the intermediate server.

Claims

1. A method for mediating a web page at an intermediate server comprising:

recording a request for a web page as a first portion of a user path;

retrieving the web page from a target web server;

ensuring that the web page will not be cached;

identifying an absolute URL in the web page according to a protocol;

changing the absolute URL to refer to the intermediate server;

identifying a resource according to a resource source tag in the web page;

mediating a link to the resource with a resource marking to indicate that a resource returned in response to a subsequent resource request including the resource marking should not be mediated;

receiving a subsequent resource request for the resource; and

retrieving the resource and returning the resource to the web browser without recording the subsequent resource request as part of the user path.

2. The method of claim 1, further comprising changing a relative URL in the web page to refer to the intermediate server.

3. The method of claim 1, further comprising recording a set of creation details for a cookie.

4. The method of claim 1, wherein the step of ensuring that the web page will not be cached comprises setting the web page to expire immediately.

5. The method of claim 1, further comprising:

changing a relative link in the web page to refer to the intermediate server, further comprising;

if the relative link contains a base tag, modify the base tag to refer to the intermediate server; and

if the relative link does not contain the base tag, insert a reference base tag, wherein the reference base tag refers to the intermediate server.

6. A method for storing user paths through web pages:

receiving a request for a first web page at an intermediate server;

recording the request as a first portion of a user path;

requesting the first web page from a target web server hosting the first web page;

retrieving the first web page from a the target web server;

ensuring that the first web page will not be cached;

changing a plurality of links in the first web page to refer to the intermediate server to create a mediated web page, wherein changing the plurality of links further comprises changing at least one dynamic link to refer to the intermediate server;

identifying a resource according to a resource source tag in the first web page; and

mediating a link to the resource with a resource marking to indicate that a resource returned in response to a subsequent resource request including the resource marking should not be mediated;

receiving a subsequent request for a second web page based on the mediated web page;

identifying the resource according to a resource source tag in the second web page;

recording the subsequent request for a second web page as a second portion of the user path at the intermediate server; and

retrieving the resource and returning the resource to the web browser without recording the subsequent resource request as part of the user path, including requesting the second web page from a target web server hosting the second web page.

7. The method of claim 6, wherein the dynamic link is a relative link, and the step of changing a relative link in the web page further comprises:

if the relative link contains a base tag, modifying the base tag to refer to the intermediate server; and

if the relative link does not contain the base tag, inserting a reference base tag, wherein the reference base tag refers to the intermediate server.

8. The method of claim 6, wherein the step of ensuring that the first web page will not be cached comprises setting the web page to expire immediately.

9. The method of claim 6, wherein the dynamic link is an absolute URL, and further comprising identifying the absolute URL by a protocol specified in the absolute URL.

10. The method of claim 6, wherein the step of changing a dynamic link to refer to the intermediate server further comprises using a host name to define the target web server associated with the first web page.

11. The method of claim 6, wherein the step of changing a dynamic link to refer to the intermediate server further comprises using a port to define the target web server associated with the first web page.

12. The method of claim 6, further comprising:

identifying a resource type according to a resource source tag in the first web page; and

mediating a link to the resource with a resource marking to indicate that a resource returned in response to a subsequent resource request including the resource marking should not be mediated.

13. The method of claim 12, wherein the resource source tag indicates that a resource is an image.

14. The method of claim 6, further comprising changing a document.domain script command to refer to a domain for the intermediate server.

15. The method of claim 6, further comprising recording a set of creation details for a first cookie at the intermediate server.

16. The method of claim 15, wherein the set of creation details is recorded from an http-header.

17. The method of claim 15, further comprising causing a browser to send a second cookie to the intermediate server, wherein the second cookie includes the set of creation details for the first cookie.

18. The method of claim 6, further comprising changing a form GET submission to a form POST submission.

19. A system for mediating a web page at an intermediate server comprising:

a computer readable medium; and

software instructions stored on the computer readable medium, wherein the software instructions are executable to;

receive a request for a first web page at an intermediate server;

record the request as a first portion of a user path;

request the first web page from a target web server hosting the first web page;

retrieve the first web page from the target web server;

ensure that the first web page will not be cached;

change a plurality of links in the first web page to refer to the intermediate server to create a mediated web page, wherein changing the plurality of links further comprises changing at least one dynamic link to refer to the intermediate server;

identify a resource according to a resource source tag in the first web page; and

mediate a link to the resource with a resource marking to indicate that a resource returned in response to a subsequent resource request including the resource marking should not be mediated;

receive a subsequent request for a second web page based on the mediated web page;

identify the resource type according to a resource source tag in the second web page;

record the subsequent request for a second web page as a second portion of the user path at the intermediate server; and

retrieve the resource and returning the resource to the web browser without recording the subsequent resource request as part of the user path, including requesting the second web page from a target web server hosting the second web page.

20. The system of claim 19, wherein the software instructions are further executable to ensure that the first web page will not be cached by setting the web page to expire immediately.

21. The system of claim 19, wherein the dynamic link is a relative link, and wherein the software instructions are further executable to:

if the relative link contains a base tag, modify the base tag to refer to the intermediate server; and

if the relative link does not contain the base tag, insert a reference base tag, wherein the reference base tag refers to the intermediate server.

22. The system of claim 19, wherein the software instructions are further executable to use a host name to define the target web server associated with the first web page.

23. The system of claim 19, wherein the software instructions are further executable to use a port to define the target web server associated with the first web page.

24. The system of claim 19, wherein the dynamic link is an absolute URL, and wherein the software instructions are further executable to identify the absolute URL by a protocol.

25. The system of claim 19, wherein the software instructions are further executable to change a document.domain script command to refer to a domain for the intermediate server.

26. The system of claim 19, wherein the software instructions are further executable to record a set of creation details for a first cookie.

27. The system of claim 26, wherein the software instructions are further executable to record the set of creation details from an http-header.

28. The system of claim 26, wherein the software instructions are further executable to cause a browser to send a second cookie to the intermediate server, wherein the second cookie includes the set of creation details for the first cookie.

29. The system of claim 19, wherein the software instructions are further executable to change a form GET submission to a form POST submission.

30. A method of mediating a web page comprising:

at an intermediate server;

receiving a web page request from a browser;

recording the web page request as part of a user path;

forwarding the web page request to a target web server;

receiving the web page from the target web server;

changing supported links in the web page to refer to the intermediate server to create mediated content, wherein changing supported links further comprises;

identifying a resource according to a resource source tag in the web page; and

mediating a link to the resource with a resource marking to indicate that a resource returned in response to a subsequent resource request including the resource marking should not be mediated;

forwarding the mediated content to the web browser, wherein the mediated content includes the resource marking; and

receiving the subsequent resource request from the browser for the resource;

retrieving the resource and returning the resource to the web browser without recording the subsequent resource request as part of the user path;

at the browser;

generating the resource request that includes the resource marking based on the mediated content.

31. The method of claim 30, further comprising:

at the intermediate server;

distinguishing the resource request from a new web page request based on the resource marking.

32. The method of claim 30, further comprising:

at the intermediate server;

recording the creation details of a first cookie;

causing the browser to send a second cookie to the intermediate server that contains the creation details of the first cookie; and

at the browser;

generating the second cookie containing the creation details of the first cookie; and

sending the second cookie to the intermediate server.