RFC1867 was updated by RFC2388

.IP "-F/--form <name=content>"

(HTTP) This lets curl emulate a filled-in form in which a user has pressed the

submit button. This causes curl to POST data using the Content-Type

multipart/form-data according to RFC1867. This enables uploading of binary

multipart/form-data according to RFC2388. This enables uploading of binary

files etc. To force the 'content' part to be a file, prefix the file name

with an @ sign. To just get the content part from a file, prefix the file name

with the symbol <. The difference between @ and < is then that @ makes a file

Using POST with HTTP 1.1 implies the use of a "Expect: 100-continue" header.

You can disable this header with \fICURLOPT_HTTPHEADER\fP as usual.

To make multipart/formdata posts (aka rfc1867-posts), check out the

To make multipart/formdata posts (aka RFC2388-posts), check out the

\fICURLOPT_HTTPPOST\fP option.

.IP CURLOPT_POSTFIELDSIZE

If you want to post data to the server without letting libcurl do a strlen()

.ad

.SH DESCRIPTION

curl_formadd() is used to append sections when building a multipart/formdata

HTTP POST (sometimes referred to as rfc1867-style posts). Append one section at

HTTP POST (sometimes referred to as RFC2388-style posts). Append one section at

a time until you've added all the sections you want included and then you pass

the \fIfirstitem\fP pointer as parameter to \fBCURLOPT_HTTPPOST\fP.

\fIlastitem\fP is set after each call and on repeated invokes it should be

While the simple examples above cover the majority of all cases where HTTP

POST operations are required, they don't do multi-part formposts. Multi-part

formposts were introduced as a better way to post (possibly large) binary data

and were first documented in the RFC1867. They're called multi-part because

they're built by a chain of parts, each being a single unit. Each part has its

own name and contents. You can in fact create and post a multi-part formpost

with the regular libcurl POST support described above, but that would require

that you build a formpost yourself and provide to libcurl. To make that

easier, libcurl provides \fIcurl_formadd(3)\fP. Using this function, you add

parts to the form. When you're done adding parts, you post the whole form.

and were first documented in the RFC1867 (updated in RFC2388). They're called

multi-part because they're built by a chain of parts, each part being a single

unit of data. Each part has its own name and contents. You can in fact create

and post a multi-part formpost with the regular libcurl POST support described

above, but that would require that you build a formpost yourself and provide

to libcurl. To make that easier, libcurl provides \fIcurl_formadd(3)\fP. Using

this function, you add parts to the form. When you're done adding parts, you

post the whole form.

The following example sets two simple text parts with plain textual contents,

and then a file with binary contents and uploads the whole thing.