I'm defining a PUT request with a JSON request body using libcurl in C.
This how I'm doing it:
sprintf(jsonObj, "\"name\" : \"%s\", \"age\" : \"%s\"", name, age);
struct curl_slist *headers = NULL;
curl_slist_append(headers, "Accept: application/json");
curl_slist_append(headers, "Content-Type: application/json");
curl_slist_append(headers, "charsets: utf-8");
curl_easy_setopt(curl, CURLOPT_URL, url);
curl_easy_setopt(curl, CURLOPT_CUSTOMREQUEST, "PUT");
curl_easy_setopt(curl, CURLOPT_HTTPHEADER, headers);
curl_easy_setopt(curl, CURLOPT_POSTFIELDS, jsonObj);
curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, WriteMemoryCallback);
curl_easy_setopt(curl, CURLOPT_WRITEDATA, (void *)&chunk);
curl_easy_setopt(curl, CURLOPT_USERAGENT, "libcrp/0.1");
res = curl_easy_perform(curl);
The request body is arriving like this:
{ '"name" : "Pedro", "age" : "22"' }
With { '
at the start and ' }
at the end.
--- MORE INFO -----
if I declare this code
char* jsonObj = "{ \"name\" : \"Pedro\" , \"age\" : \"22\" }";
struct curl_slist *headers = NULL;
curl_slist_append(headers, "Accept: application/json");
curl_slist_append(headers, "Content-Type: application/json");
curl_slist_append(headers, "charsets: utf-8");
curl_easy_setopt(curl, CURLOPT_URL, url);
curl_easy_setopt(curl, CURLOPT_CUSTOMREQUEST, "PUT");
curl_easy_setopt(curl, CURLOPT_HTTPHEADER, headers);
curl_easy_setopt(curl, CURLOPT_POSTFIELDS, jsonObj);
curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, WriteMemoryCallback);
curl_easy_setopt(curl, CURLOPT_WRITEDATA, (void *)&chunk);
curl_easy_setopt(curl, CURLOPT_USERAGENT, "libcrp/0.1");
res = curl_easy_perform(curl);
the server receives this as the request body:
{ '{ "name" : "Pedro" , "age" : "22" }': '' }
My question is:
Is the libCurl pre-formatting/encoding automatically the Json request?
By the way, does the libCurl have some way of encoding a JSON object?
Thanks so much!
libcurl will send exactly the bytes you ask it to send. It has no knowledge of JSON at all.
See @Lukasa's excellent and more elaborate answer for better and more details.
I was having a similar Issue.
I discovered the -libcurl option for the curl command. It helped a lot! Just add it to the end of your working curl command.
In the end it help me create this code:
Express recieves this JSON as:
I hope this helps!
The problem may be with the headers. When you are configuring your curl_slist headers I think you should assign the output of curl_slist_append back to headers:
A key part of understanding whether the system is behaving correctly is seeing what the program is actually sending over the network. So another way to check the byte stream, instead of pointing it at your server (and/or running Wireshark), is to just run a netcat instance in a separate window on the test machine:
and point the code (CURLOPT_URL) at "http://localhost:8080".
You'll need to hit Control-D in the
nc
window to terminate the connection so that curl completes, but you can also type a test return text beforehand, which can be useful if you're expecting some sort of reply to test against.Firstly, let's note a few things. To start with, Daniel Stenberg is correct (as I'd hope he would be, given that he wrote the code): libcurl does not append any data to your code. I can demonstrate this with this sample program, which is like your example but with some additional setup/teardown code. This is all of the code: there is nothing else present here:
Packet capturing the request with Wireshark shows that this emits the following HTTP request:
As you can see, this is exactly the JSON data you asked to send. There is no extra data here, no enclosing braces.
This means that the extra braces are being added either by your server or by some intermediate middlebox. My guess is that your server is adding it because it is forcibly trying to turn any body that is not an
application/json
body into one by considering the entire body a string.The reason your server doesn't consider this a JSON body is encapsulated by another answer here: you aren't setting your headers properly.
curl_slist_append
returns a newstruct curl_slist *
that you need to assign back into yourheaders
variable. That means you need to change these four lines:to these four:
This should convince your server that you are sending JSON data.
In the future, I recommend you get familiar with Wireshark for solving problems like this. It is extremely helpful to see the actual request you sent. Failing that, if you'd rather not, you can use
CURLOPT_DEBUGFUNCTION
to grab the data curl is sending to validate it.I used json-c for encoding and decoding jsons and it worked very well. The documentation is also easy to understand. https://linuxprograms.wordpress.com/2010/05/20/json-c-libjson-tutorial/