HTTP transaction monitor with replay capacity

• US 20020156881A1
• Filed: 02/20/2001
• Published: 10/24/2002
• Est. Priority Date: 10/03/2000
• Status: Abandoned Application

• Current Assignee: Ana H. Von Klopp Lemon, George C. Finklang
• Original Assignee: Ana H. Von Klopp Lemon, George C. Finklang
• Inventors: Klopp Lemon, Ana H. von, Finklang, George C.
• Application Number:
  US09/789,238
• Publication Number:
  US 20020156881A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 43/18 Protocol analysers
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system for monitoring HTTP transactions between a server and a client includes a data collector which runs on the server and collects data from HTTP requests sent by the client to the server and data from the HTTP responses sent by the server to the client. The system also includes a graphical display which displays the collected data and through which replay requests are sent to the server, each replay request specifying a prior HTTP request to be interpreted by the server. The system also includes a request player which runs on the server and modifies each replay request with a portion of the collected data associated with the prior HTTP request to be interpreted by the server.

Claims

1. A system for monitoring HTTP transactions between a server and a client, comprising:

a data collector which runs on the server and collects data from HTTP requests sent by the client to the server and data from HTTP responses sent by the server to the client;

a graphical display which displays the collected data and through which replay requests are sent to the server, each replay request specifying a prior HTTP request to be interpreted by the server; and

a request player which runs on the server and modifies each replay request with a portion of the collected data associated with the prior HTTP request to be interpreted by the server.

2. The system of claim 1, wherein the request player modifies the replay requests prior to the server interpreting the replay requests.

3. The system of claim 2, wherein the request player comprises a process which uses a hook in the server to intercept the replay requests in order to modify the replay requests.

4. The system of claim 2, wherein the request player comprises a process which uses a hook in a server plug-in to intercept the replay requests in order to modify the replay requests.

5. The system of claim 1, wherein the data collector collects data from the HTTP requests prior to the server interpreting the HTTP requests.

6. The system of claim 5, wherein the data collector collects data from the HTTP responses prior to the server sending the HTTP responses to the client.

7. The system of claim 6, wherein the data collector comprises a process which uses a hook in the server to intercept the HTTP requests and the HTTP responses in order to collect data from the HTTP requests and the HTTP responses.

8. The system of claim 6, wherein the data collector comprises a process which uses a hook in a server plug-in to intercept the HTTP requests and the HTTP responses in order to collect data from the HTTP requests and the HTTP responses.

9. The system of claim 1, wherein the collected data are stored in a directory on the server.

10. The system of claim 9, further comprising means for retrieving the collected data from the directory and serving the data to the request player and the graphical display.

11. The system of claim 1, wherein an application which provides the graphical display manages the collected data.

12. The system of claim 1, further comprising means for notifying the graphical display when new data is collected by the data collector.

14. The system of claim 13, wherein the request player modifies the replay requests prior to the server interpreting the replay requests.

15. The system of claim 14, wherein the request player comprises a process which uses a hook in the server to intercept the replay requests in order to modify the replay requests.

16. The system of claim 14, wherein the request player comprises a process which uses a hook in a server plug-in to intercept the replay requests in order to modify the replay requests.

17. The system of claim 13, wherein the data collector collects data from the HTTP requests prior to the server executing the HTTP requests.

18. The system of claim 17, wherein the data collector collects data from the HTTP responses prior to the HTTP responses leaving the server.

19. The system of claim 18, wherein the data collector comprises a process which uses a hook in the server to intercept the HTTP requests and the HTTP responses in order to collect data from the HTTP requests and the HTTP responses.

20. The system of claim 18, wherein the data collector comprises a process which uses a hook in a server plug-in to intercept the HTTP requests and the HTTP responses in order to collect data from the HTTP requests and the HTTP responses.

13. A system for monitoring data flow in a web application, comprising:

a server which hosts the web application;

a client which accesses components of the web application by sending HTTP requests to the server and receiving HTTP responses from the server;

a data collector which runs on the server and collects data from the HTTP requests and the HTTP responses;

a graphical display which displays the collected data and through which replay requests are sent to the server, each replay request specifying a prior HTTP request to be interpreted by the server;

a request player which runs on the server and modifies each replay request with a portion of the collected data corresponding to the prior HTTP request to be interpreted by the server.

21. A system for testing and debugging a web application, comprising:

a server which hosts the web application;

a client which accesses components of the web application by sending HTTP requests to the server and receiving HTTP responses from the server;

a data collector which runs on the server and collects data from the HTTP requests and the HTTP responses;

a graphical display which displays the collected data and through which HTTP replay requests are sent to the server, each HTTP replay request specifying a prior HTTP request to be interpreted by the server;

a request player which runs on the server and modifies each HTTP replay request with a portion of the collected data corresponding to the prior HTTP request to be interpreted by the server;

an application which starts the server in a separate process and through which the graphical display can be accessed.

22. The system of claim 21, wherein the application is an integrated development environment for a web application.

23. The system of claim 22, wherein the client is accessible from within the integrated development environment.

24. The system of claim 22, wherein the application includes an internal server.

25. The system of claim 24, wherein the internal server updates the graphical display with the collected data.

27. The method of claim 26, wherein the replay request is initiated through the graphical display.

26. A method for monitoring data flow in a web application, comprising:

using a client to send a HTTP request to a server hosting the web application;

using the client to receive a HTTP response from the server;

prior to the server interpreting the HTTP request, determining if the HTTP request is a replay request which specifies a prior HTTP request to be interpreted by the server and, if the HTTP request is a replay request, modifying the HTTP request with request data associated with the prior HTTP request to be interpreted;

collecting data from the HTTP request prior to the server interpreting the HTTP request;

collecting data from the HTTP response prior to the server sending the HTTP response to the client; and

displaying the collected data in a graphical display.