Reputation: 59
I noticed this when analyzing wireshark. under thread group those requests are:
on wireshark there are some other requests that jmeter sends. but when i test this with browser, that requests wont be send.
after request 2) HTTP GET /Content/css?v=........... HTTP/1.1\r\n HTTP GET /Content/cus-css-plugins?v=......-..... HTTP/1.1\r\n HTTP GET /images/logo/logo.._...png HTTP/1.1\r\n and so on, totally 6 inintended requests are sent. there are not in the sampler list. and not sent when using browser.
the test script is recorded by blazemeter chrome plugin.
another unintended request HTTP GET /signalr/hubs HTTP/1.1\r\n is sent by jmeter, but it is also sent when using browser. because it is not in the sample list, the "Accept" field is very different between browser and jmeter. it is another issue. so, should i add this request to jmeter manually and control the fields?
Upvotes: 0
Views: 91
Reputation: 168052
BlazeMeter Chrome Extension generates a JMeter Test Plan with HTTP Request Defaults configuration element configured to "Retrieve Resources from HTML Files"
This is normal as it replicates real browser behaviour, real browsers download the HTML content from the response and then execute parallel HTTP Requests to download images, scripts, styles, fonts, sounds, etc. and this setting instructs JMeter to behave like a real browser when it comes to these embedded resources handling.
If you open your browser developer tools you should see the same requests (just tick "Disable cache" if you don't see them)
More information: Web Testing with JMeter: How To Properly Handle Embedded Resources in HTML Responses
Upvotes: 1