Skip to main content

Recording curl request with JMeter Recorder

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 127.0.0.1 (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 127.0.0.1:8090 flag. The curl request looks as - 

curl -k --proxy 127.0.0.1:8090 -X POST --header 'Content-Type: multipart/form-data' --header 'Accept: application/json' --header 'Authorization: bearer xxx' -F upload_file=@"/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. 

And this solved the issue of 400 error when uploading document using JMeter :) 

Popular posts from this blog

Distributed Load Testing with JMeter

Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

XPath and single quotes

I had tough time dealing with XPath and single quote. Though W3C recommends using ' to escape it but I never got it working, let me know if any of you get through. Came across this blog and found that “concat” could be used in this situation. So original XPath expression is – //meta[@name=’DESCRIPTION’][@content=’Tester’s Test’] This is some thing which certainly fails as single quote in “Tester’s” marks it at end of string and then XPath blows up, next trial was – //meta[@name=’DESCRIPTION’][@content=’Tester''s Test’] This does not work despite w3c recommendation! And then I used concat function and split the string as – concat(‘Tester’,”’”,’s Test’) NOTICE that single quote is kept in double quote while other characters are kept in single quotes. So XPath looks as – //meta[@name=’DESCRIPTION’][@content=concat(‘Tester’,”’”,’s Test’)] And this works charm.