It worked for me. Based on what I read on the Internet, various options were suggested:
- Changing the encoding of content in UTF-8
- Pass the PUT parameters on the body data tab (as opposed to transferring them in tabular format on the Parameters tab).
- Configure Content-Type header on application / json in HTTP Header Manager
- Passing parameters through a file (even if this should work, how would you pass dynamic values?)
- passing it as a POST with a combination of the above points.
WHAT WORKS FOR ME is a combination: Set the content type for the application / json + Transfer parameters as "JSON" in the body data ** strong> (below example)
I did not need to specify UTF-8 or anything else.
JSON PARAMETER BODY EXAMPLE: {"Name": "JMeterTitle", "preMortar": "JMeterPre", "postMortar": "JMeterPost"}
source share