Proxy server for testing

How does the magic lasso of the HTTP Proxy Server work?

JMeter HTTP Proxy ServerJMeter has a major superpower: the ability to record traffic in a single bound (or, in non super hero speak, as it happens).

This feature allows testers to avoid the long and tedious task of manually recording traffic and simply automates the task. The HTTP Proxy Server is the tool the superpower operates through, much like Wonder Woman's magic lasso ;).

The Proxy Server allows JMeter to watch and record actions while users browse web application with standard browsers. JMeter will create test sample objects and store them directly into the test plan as the user browses (so samples can be interactively viewed in real time).

Create a new test-plan and switch to WorkBench. Then go to “WorkBench”->”Add”->”Non-Test Elements”->”HTTP Proxy server”.

Connection Settings

The first thing we have to do is set up the browser for traffic recording.

Specify the free port that can be used for the proxy. This port should not be occupied with another server. Our tester used a WAMP server with the testing application installed on the PC, so we changed the default port 8080 to 8090. Then open your browser network settings (We used Mozilla Firefox).

Set “Manual proxy configuration” and specify for the HTTP Proxy, because the HTTP Proxy server will work on the local host. Do not forget to set the same port as in proxy server settings, e.g. 8090. Next, add the recording controller for collecting HTTP requests.

JMeter Test PlanThe Recording Controller is a placeholder indicating where the proxy server should record samples to.

During the test run, it has no effect. But during the recording, use the HTTP Proxy Server and all recorded samples will be saved by default under the Recording Controller.

Set up patterns of traffic recording. You know, that typical web page that consists not only of dynamic PHP or JavaScript or whatever else but, also has static content such as pictures or icons. If you prefer to work exclusively with dynamic pages, then filter unwanted traffic either during recording or manually during debugging. Super easy to do during recording.

Note that the table forms URL Patterns to exclude. If you leave this form empty, all incoming traffic will be recorded and placed into the Recording Controller. But if you specify patterns for target URLs, then the HTTP Proxy Server will filter URLs that match the pattern.


Related posts:

  1. Proxy server Review
  2. Proxy server refusing
  3. Proxy server Streaming
  4. Proxy server for Torrenting