Recording curl request with JMeter Recorder

By | April 15, 2018

Though it is quite east to convert curl requests to corresponding JMeter request. At times you might be stuck with issue like I faced when uploading a file with JMeter HTTP request

In a gist I kept getting 404 error when using REStful service to upload a file. After days of investigations I found it that I should be using HTTP request implementation java and not HttpClient4. JMeter HTTPs Test Script recorder was of great help to debug this issue. This post describes the process of recording curl request through JMeter HTTPs Test Script recorder.
If you have never used JMeter HTTPs Test Script recorder then create a new JMeter Plan and under WorkBench > Add > Non Test Element > HTTP(s) Test Script Recorder.
Specify Global Setting > Port as 8090
If we were using browser to record web application then we would configure its proxy to (Since http proxy server would work on localhost) and port 8090 –

Any way, we are not going to record browser actions but a curl request.
Under Test Plan element add Thread Group, Recording Controller and HTTP Request Default. Under HTTP Request Defaults mention Server IP as localhost” and port as 8090. This is to avoid duplication from HTTP Requests during recording. Recording Controller is where recorded samples would appear.
In the end Test Plan would looks as –
To be able to record curl request on JMeter, we have to specify proxy server on curl using –proxy flag. The curl request looks as –
curl -k –proxy -X POST –header ‘Content-Type: multipart/form-data’ –header ‘Accept: application/json’ –header ‘Authorization: bearer xxx’ -F [email protected]”/Users/tbhadauria/Documents/test.pdf”  ‘https://xxx
Notice that I also added flag “k” to turn off curl’s verification of certificate. Now hit the “Start” button on HTTPs Test Script Recorder and execute curl command. Following this you would find recorded elements under Recording Controller as following –
I had already setup curl request on JMeter and comparing it to recorded elements I found that the only difference was the HTTP Request Implementation. I was using HTTP Request Implementation HTTPClient4 which would result in 400 error while recorded element had HTTP Request Implementation Java and it worked successfully.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.