Request Capture is the ability to store incoming requests and their associated responses to the file system.
When request capture is set to requests and responses you will end up with three files for each request. A request file, a body file and a response file. The header XML file holds all information sent to server by the client. The response XML file holds everything sent back (besides body) and the body file holds the actual returned content.
WARNING: Turning on Request Content Capture will create multiple XML files for every request run on a server. This may use very large quantities of disk space quickly. Please be careful when enabling this feature and do not leave it enabled if you are not monitoring it.
From the FusionReactor Administrator, click "Request Settings" from the table of contents (Requests section) and you will see the Request Settings screen. Scroll down until you reach a section named "Request Capture". From here you can control the request capture feature.]
Request Capture can be in three states. Disabled, Capture Requests only, or capture both requests and responses. The Capture Path is the directory into which the captured requests will be stored.
Request capture can be useful for a variety of reasons from technical to legal, these include:
The FusionReactor stored requests hold much more information than you would normally expect to find in web logs and as such they have a much higher value for analyzing your application traffic.
You could use stored requests in order to be able to reproduce specific load conditions or test cases.
Anyone who has had to have a user describe the contents of their screen will instantly realize how much easier life would be if you had an exact copy of their response in easy access.