HTTP transaction monitor with edit and replay capacity
First Claim
Patent Images
1_9. ] A mechanism for monitoring data flow in a web application hosted on a server, comprising:
- a directory in which HTTP transactions processed on the server are stored;
a display through which a request associated with a selected HTTP transaction in the directory can be re-executed in order to recreate the selected HTTP transaction; and
an editor through which request data associated with the request can be modified prior to re-executing the request.
1 Assignment
0 Petitions
Accused Products
Abstract
A mechanism for monitoring data flow in a web application hosted on a server includes a directory in which HTTP transactions processed on the server are stored, a display through which a request associated with a selected HTTP transaction in the directory can be re-executed in order to recreate the selected HTTP transaction, and an editor through which request data associated with the request can be modified prior to re-executing the request.
-
Citations
349 Claims
-
1_9. ] A mechanism for monitoring data flow in a web application hosted on a server, comprising:
-
a directory in which HTTP transactions processed on the server are stored;
a display through which a request associated with a selected HTTP transaction in the directory can be re-executed in order to recreate the selected HTTP transaction; and
an editor through which request data associated with the request can be modified prior to re-executing the request.
-
-
2_9. ] The mechanism of claim 1, further comprising a request player that reconstructs the request using an output of the editor.
-
3_9. ] The mechanism of claim 2, wherein the output of the editor comprises a modification of the request data.
-
4_9. ] The mechanism of claim 3, wherein the modification of the request data is stored in the directory.
-
5_9. ] The mechanism of claim 4, further comprising means for retrieving the modification of the request data from the directory.
-
6_9. ] The mechanism of claim 1, further comprising a data collector that selectively intercepts the HTTP transactions processed on the server in order to collect data passed between components of the web application.
-
7_9. ] The mechanism of claim 6, further comprising means for storing the data collected by the data collector in the directory.
-
8_9. ] The mechanism of claim 6, further comprising means for notifying the display of data collected by the data collector.
-
9_9. ] A mechanism for monitoring data flow in a web application hosted on a server, comprising:
-
a data collector that selectively intercepts HTTP transactions processed on the server in order to collect data passed between components of the web application;
a display through which a request associated with a selected HTTP transaction for which data has been collected can be sent to the server; and
an editor through which request data associated with the request can be modified prior to re-executing the request.
-
-
10_9. ] The mechanism of claim 9, further comprising a request player that reconstructs the request using an output of the editor.
-
11_9. ] The mechanism of claim 10, wherein the output of the editor includes a modification of the request data.
-
12_9. ] The mechanism of claim 11, wherein the modification of the request data is stored in a directory.
-
13_9. ] The mechanism of claim 12, further comprising means for retrieving the modification of the request data from the directory.
-
14_9. ] The mechanism of claim 12, further comprising means for storing the data collected by the data collector in the directory.
-
15_9. ] A method for monitoring data flow in a web application hosted on a server, comprising:
-
obtaining an HTTP transaction processed on the server while interacting with the web application, the HTTP transaction having an associated request;
editing request data associated with the request;
reconstructing the request using the edited request data; and
re-executing the request in order to recreate the HTTP transaction.
-
-
16_9. ] The method of claim 15, wherein obtaining the HTTP transaction comprises retrieving the HTTP transaction from a directory containing HTTP transactions processed on the server.
-
17_9. ] The method of claim 16, wherein obtaining the HTTP transaction further includes selecting the HTTP transaction through a display that includes a list of the HTTP transactions in the directory.
-
18_9. ] The method of claim 15, wherein editing request data associated with the request comprises editing a copy of the request data.
-
19_9. ] The method of claim 18, wherein editing the copy of the request data comprises storing the edited copy of the request data in a directory.
-
20_9. ] The method of claim 19, wherein re-constructing the request using the edited request data comprises retrieving the copy of the request data from the directory and associating the copy of the request data with the request.
-
21_9. ] The method of claim 15, further comprising collecting data passed between components of the web application before and after the request is re-executed.
-
22_9. ] The method of claim 21, further comprising displaying the collected data.
-
23_9. ] A system for testing and debugging a web application, comprising:
-
a server hosting the web application;
a directory in which HTTP transactions processed on the server are stored;
a client through which a request associated with a selected HTTP transaction in the directory can be re-executed in order to recreate the selected HTTP transaction; and
an editor through which request data associated with the request can be modified prior to re-executing the request.
-
-
24_9. ] The system of claim 23, wherein an output of the editor comprises a modification of the request data.
-
25_9. ] The system of claim 24, wherein the client reconstructs the request using the modification of the request data.
-
26_9. ] The system of claim 24, further comprising a request player running on the server which reconstructs the request using the modification of the request data.
-
27_9. ] The system of claim 23, further comprising a data collector running on the server which intercepts HTTP transactions processed on the server in order to collect data passed between components of the web application.
-
28_9. ] The system of claim 23, wherein the client includes an action for invoking the editor.
-
29_9. ] The system of claim 28, wherein the client includes a controller which manages access to the directory.
-
30_9. ] The system of claim 28, further comprising an application which starts the server in a separate process and through which the client can be started.
-
31_9. ] The system of claim 30, wherein the application is an integrated development environment.
-
32_9. ] The system of claim 30, wherein the application includes an internal HTTP server.
-
33_9. ] The system of claim 32, wherein the internal HTTP server includes a mechanism for receiving data from the data collector and notifying the client of the collected data.
-
34_9. ] A mechanism for monitoring data flow in a web application hosted on a server, comprising:
-
means for storing HTTP transactions processed on the server;
means for re-executing a request associated with a selected HTTP transaction in the directory in order to recreate the selected HTTP transaction; and
means for modifying request data associated with the request prior to re-executing the request.
-
Specification