generic-library/curl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

spell out that POSTFIELDS should be url-encoded in most cases

Browse Source
This commit is contained in:
Daniel Stenberg 2003-02-28 07:53:31 +00:00
parent a3d3642a30
commit bc1102922b
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/libcurl/curl_easy_setopt.3
View File

@ -361,9 +361,14 @@ will imply this option.
.TP .TP
.B CURLOPT_POSTFIELDS .B CURLOPT_POSTFIELDS
Pass a char * as parameter, which should be the full data to post in a HTTP 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 post operation. You need to make sure that the data is formatted the way you
is the most commonly used one by HTML forms. See also the CURLOPT_POST. Since want the server to receive it. libcurl will not convert or encode it for
7.8, using CURLOPT_POSTFIELDS implies CURLOPT_POST. 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 \fBNote:\fP to make multipart/formdata posts (aka rfc1867-posts), check out
the \fICURLOPT_HTTPPOST\fP option. the \fICURLOPT_HTTPPOST\fP option.