From bc1102922bd5d6b4e2a6f7a3c3b25e63897a07f6 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 28 Feb 2003 07:53:31 +0000 Subject: [PATCH] spell out that POSTFIELDS should be url-encoded in most cases --- docs/libcurl/curl_easy_setopt.3 | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index 8b3a7f30a..3f8ef88a5 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -361,9 +361,14 @@ will imply this option. .TP .B CURLOPT_POSTFIELDS Pass a char * as parameter, which should be the full data to post in a HTTP -post operation. This is a normal application/x-www-form-urlencoded kind, which -is the most commonly used one by HTML forms. See also the CURLOPT_POST. Since -7.8, using CURLOPT_POSTFIELDS implies CURLOPT_POST. +post operation. You need to make sure that the data is formatted the way you +want the server to receive it. libcurl will not convert or encode it for +you. Most web servers will assume this data to be url-encoded. Take note. + +This POST is a normal application/x-www-form-urlencoded kind (and libcurl will +set that Content-Type by default when this option is used), which is the most +commonly used one by HTML forms. See also the CURLOPT_POST. Using +CURLOPT_POSTFIELDS implies CURLOPT_POST. \fBNote:\fP to make multipart/formdata posts (aka rfc1867-posts), check out the \fICURLOPT_HTTPPOST\fP option.