Foreword
Sometimes, in order to get more detailed results of the request, we may need to use Fiddler combination Jmeter task packet analysis, in order to better assist test.
Problems encountered
Here to get a student information interface as an example.
When I press the interface documentation set correctly in the request Jmeter, open Fiddler, I found it impossible to catch Jmeter request.
You can see from the picture, Fiddler has not caught request Jmeter sent.
problem analysis
Simple analysis, Fiddler in the course is based on the proxy form from the Web server, the proxy address is 127.0.0.1, port 8888, which at runtime will monitor HTTP proxy port 8888.
Thus, when we Jmeter the current request, the proxy address and port is provided aligned with Fiddler, Fiddler should be able to fetch the requested data Jmeter transmitted.
Agent request provided Jmeter
We currently have two HTTP requests, we first set up only one.
After the setup is complete, execute the test plan again.
Can be seen, the Fiddler crawled first request and the second request because the agent is not provided, so that the data did not catch.
Set Default HTTP request
If we have a lot of requests, we can not always in every request proxy settings are right, therefore, we'd set up a HTTP Request Defaults.
We just need the HTTP request defaults set up a proxy server, then the request will use the back of the HTTP request defaults set the default value, so that our request will be able to crawl Fiddler.
Note: When closing Fiddler, we need to disable the HTTP Request Defaults Jmeter to cancel the current proxy settings, otherwise Jmeter may not request properly.