JMeter Proxy Settings for Recording and Test Execution
The browser uses the recorder during capture; JMeter's own HTTP client sends the later load test.
| Activity | Route to configure |
|---|---|
| Record browser traffic | Browser → recorder; required onward proxy on that path |
| Run generated HTTP test | JMeter HTTP client → intended upstream/destination |
A successful recorded page says nothing about the later client's proxy/account settings. Inspect those before executing the plan.
Keep recorder listener, upstream proxy and application destination as three addresses. A local recorder port is neither the application's service port nor a public exit for unrelated machines; the recording browser needs reachability within its intended boundary.
HTTPS interception during authorized recording requires the temporary browser trust arrangement. For an mTLS application, the recorder also needs its authorized client identity for the onward connection. Reachability and upstream authentication remain separate, and that recording CA is not a permanent ordinary-browsing requirement.
Restore the browser's intended settings after capture. The next test run must then be judged on JMeter's own route.