When investigating issues, you often need to look at what goes "over the wire", in the HTTP requests between the client and the server. You may want to look at the HTTP requests as sent/received on the browser, on the application server, or somewhere in between. This page lists a few tool which might be of use in these cases.
WireShark is a workhorse. It can do a lot more than monitoring HTTP requests, but can also be intimidating. Lately, usability, including the installing process, has improved significantly. (See below for more details on WireShark.)
Request Dumper Filter; see below
On Tomcat, you can use the Request Dumper Valve; see below
Use the browser's dev tools (AKA "F12 Developer Tools" on IE)
On Firefox, use Firebug's Net tab, or the Console tab for Ajax requests.
After you install WireShark, click on Capture Options, and setup a setup the Capture Filter to be
tcp port 8080. (Replace
8080 with the port on which your application server or services are listening, as appropriate.)
Click Start, and since you only interested about HTTP (versus TCP) traffic, in Filter type
http and press enter to apply.
Next WireShark will show you all the HTTP traffic that goes through the machine it is running on, to the port you specified (here 8080).
Note that the Request Dumper Filter only shows information about the HTTP headers of the request. If you want more information to be logged, use the Apache TCPMon.
The Request Dumper Filter comes with Tomcat, so even if you are not using Tomcat, start by downloading Tomcat.
Unzip Tomcat, and copy the directory webapps/servlets-examples/WEB-INF/classes/filters to the WEB-INF/classes directory of your web application.
Edit WEB-INF/web.xml and add:
After the declaration of the filter ops-xforms-filter:
After the filter mapping for ops-xforms-filter:
Restart your application server (e.g. Tomcat).
On Tomcat, requests will be logged to the logs/localhost log file.
The Request Dumper Valve doesn't log the body of
POSTs, it can only be used on Tomcat, and we found its output to be less readable than what you get with the Request Dumper Filter. But if you still want to experiment with the Request Dumper Valve, add the following in server.xml inside :