mirror of
https://github.com/ENSL/NS.git
synced 2024-12-03 09:42:00 +00:00
8552ac617c
git-svn-id: https://unknownworlds.svn.cloudforge.com/ns1@1 67975925-1194-0748-b3d5-c16f83f1a3a1
286 lines
11 KiB
HTML
286 lines
11 KiB
HTML
<HTML>
|
|
<BODY>
|
|
<PRE>
|
|
<!-- Manpage converted by man2html 3.0.1 -->
|
|
curl_formadd - add a section to a multipart/formdata HTTP
|
|
POST
|
|
|
|
|
|
</PRE>
|
|
<H2>SYNOPSIS</H2><PRE>
|
|
<B>#include</B> <B><curl/curl.h></B>
|
|
|
|
<B>CURLFORMcode</B> <B>curl_formadd(struct</B> <B>HttpPost</B> <B>**</B> <I>firstitem,</I>
|
|
<B>struct</B> <B>HttpPost</B> <B>**</B> <I>lastitem,</I> <B>...);</B>
|
|
|
|
|
|
</PRE>
|
|
<H2>DESCRIPTION</H2><PRE>
|
|
curl_formadd() is used to append sections when building a
|
|
multipart/formdata HTTP POST (sometimes refered to as
|
|
rfc1867-style posts). Append one section at a time until
|
|
you've added all the sections you want included and then
|
|
you pass the <I>firstitem</I> pointer as parameter to <B>CUR-</B>
|
|
<B>LOPT_HTTPPOST</B>. <I>lastitem</I> is set after each call and on
|
|
repeated invokes it should be left as set to allow
|
|
repeated invokes to find the end of the list faster.
|
|
|
|
After the <I>lastitem</I> pointer follow the real arguments.
|
|
|
|
The pointers <I>*firstitem</I> and <I>*lastitem</I> should both be
|
|
pointing to NULL in the first call to this function. All
|
|
list-data will be allocated by the function itself. You
|
|
must call <I>curl</I><B>_</B><I>formfree</I> after the form post has been done
|
|
to free the resources again.
|
|
|
|
First, there are some basics you need to understand about
|
|
multipart/formdata posts. Each part consists of at least a
|
|
NAME and a CONTENTS part. If the part is made for file
|
|
upload, there are also a stored CONTENT-TYPE and a FILE-
|
|
NAME. Below here, we'll discuss on what options you use to
|
|
set these properties in the parts you want to add to your
|
|
post.
|
|
|
|
|
|
</PRE>
|
|
<H2>OPTIONS</H2><PRE>
|
|
<B>CURLFORM_COPYNAME</B> followed by string is used to set the
|
|
name of this part. libcurl copies the given data, so your
|
|
application doesn't need to keep it around after this
|
|
function call. If the name isn't zero terminated properly,
|
|
or if you'd like it to contain zero bytes, you need to set
|
|
the length of the name with <B>CURLFORM_NAMELENGTH</B>.
|
|
|
|
<B>CURLFORM_PTRNAME</B> followed by a string is used for the name
|
|
of this part. libcurl will use the pointer and refer to
|
|
the data in your application, you must make sure it
|
|
remains until curl no longer needs it. If the name isn't
|
|
zero terminated properly, or if you'd like it to contain
|
|
zero bytes, you need to set the length of the name with
|
|
<B>CURLFORM_NAMELENGTH</B>.
|
|
|
|
<B>CURLFORM_COPYCONTENTS</B> followed by a string is used for the
|
|
need to keep it around after this function call. If the
|
|
data isn't zero terminated properly, or if you'd like it
|
|
to contain zero bytes, you need to set the length of the
|
|
name with <B>CURLFORM_CONTENTSLENGTH</B>.
|
|
|
|
<B>CURLFORM_PTRCONTENTS</B> followed by a string is used for the
|
|
contents of this part, the actual data to send away.
|
|
libcurl will use the pointer and refer to the data in your
|
|
application, you must make sure it remains until curl no
|
|
longer needs it. If the data isn't zero terminated prop-
|
|
erly, or if you'd like it to contain zero bytes, you need
|
|
to set the length of the name with <B>CURLFORM_CON-</B>
|
|
<B>TENTSLENGTH</B>.
|
|
|
|
<B>CURLFORM_FILECONTENT</B> followed by a file name, makes that
|
|
file read and the contents will be used in as data in this
|
|
part.
|
|
|
|
<B>CURLFORM_FILE</B> followed by a file name, makes this part a
|
|
file upload part. It sets the file name field to the
|
|
actual file name used here, it gets the contents of the
|
|
file and passes as data and sets the content-type if the
|
|
given file match one of the new internally known file
|
|
extension. For <B>CURLFORM_FILE</B> the user may send one or
|
|
more files in one part by providing multiple <B>CURLFORM_FILE</B>
|
|
arguments each followed by the filename (and each CURL-
|
|
FORM_FILE is allowed to have a CURLFORM_CONTENTTYPE).
|
|
|
|
<B>CURLFORM_CONTENTTYPE</B> followed by a pointer to a string
|
|
with a content-type will make curl use this given content-
|
|
type for this file upload part, possibly instead of an
|
|
internally chosen one.
|
|
|
|
<B>CURLFORM_FILENAME</B> followed by a pointer to a string to a
|
|
name, will make libcurl use the given name in the file
|
|
upload part, intead of the actual file name given to <I>CURL-</I>
|
|
<I>FORM</I><B>_</B><I>FILE</I>.
|
|
|
|
<B>BCURLFORM_BUFFER</B> followed by a string, tells libcurl that
|
|
a buffer is to be used to upload data instead of using a
|
|
file. The given string is used as the value of the file
|
|
name field in the content header.
|
|
|
|
<B>CURLFORM_BUFFERPTR</B> followed by a pointer to a data area,
|
|
tells libcurl the address of the buffer containing data to
|
|
upload (as indicated with <I>CURLFORM</I><B>_</B><I>BUFFER</I>). The buffer
|
|
containing this data must not be freed until after
|
|
curl_easy_cleanup is called.
|
|
|
|
<B>CURLFORM_BUFFERLENGTH</B> followed by a long with the size of
|
|
the <I>CURLFORM</I><B>_</B><I>BUFFERPTR</I> data area, tells libcurl the length
|
|
of the buffer to upload.
|
|
curl_formadd() is the <B>CURLFORM_ARRAY</B> option, that passes a
|
|
struct curl_forms array pointer as its value. Each
|
|
curl_forms structure element has a CURLformoption and a
|
|
char pointer. The final element in the array must be a
|
|
CURLFORM_END. All available options can be used in an
|
|
array, except the CURLFORM_ARRAY option itself! The last
|
|
argument in such an array must always be <B>CURLFORM_END</B>.
|
|
|
|
<B>CURLFORM_CONTENTHEADER</B> specifies extra headers for the
|
|
form POST section. This takes a curl_slist prepared in
|
|
the usual way using <B>curl_slist_append</B> and appends the list
|
|
of headers to those libcurl automatically generates. The
|
|
list must exist while the POST occurs, if you free it
|
|
before the post completes you may experience problems.
|
|
|
|
When you've passed the HttpPost pointer to
|
|
<I>curl</I><B>_</B><I>easy</I><B>_</B><I>setopt</I> (using the <I>CURLOPT</I><B>_</B><I>HTTPPOST</I> option), you
|
|
must not free the list until after you've called
|
|
<I>curl</I><B>_</B><I>easy</I><B>_</B><I>cleanup</I> for the curl handle.
|
|
|
|
See example below.
|
|
|
|
|
|
</PRE>
|
|
<H2>RETURN VALUE</H2><PRE>
|
|
0 means everything was ok, non-zero means an error
|
|
occurred as <I><curl/curl.h></I> defines.
|
|
|
|
|
|
</PRE>
|
|
<H2>EXAMPLE</H2><PRE>
|
|
struct HttpPost* post = NULL;
|
|
struct HttpPost* last = NULL;
|
|
char namebuffer[] = "name buffer";
|
|
long namelength = strlen(namebuffer);
|
|
char buffer[] = "test buffer";
|
|
char htmlbuffer[] = "<HTML>test buffer</HTML>";
|
|
long htmlbufferlength = strlen(htmlbuffer);
|
|
struct curl_forms forms[3];
|
|
char file1[] = "my-face.jpg";
|
|
char file2[] = "your-face.jpg";
|
|
/* add null character into htmlbuffer, to demonstrate that
|
|
transfers of buffers containing null characters actually work
|
|
*/
|
|
htmlbuffer[8] = '\0';
|
|
|
|
/* Add simple name/content section */
|
|
curl_formadd(&post, &last, CURLFORM_COPYNAME, "name",
|
|
CURLFORM_COPYCONTENTS, "content", CURLFORM_END);
|
|
|
|
/* Add simple name/content/contenttype section */
|
|
curl_formadd(&post, &last, CURLFORM_COPYNAME, "htmlcode",
|
|
CURLFORM_COPYCONTENTS, "<HTML></HTML>",
|
|
CURLFORM_CONTENTTYPE, "text/html", CURLFORM_END);
|
|
|
|
/* Add name/ptrcontent section */
|
|
|
|
/* Add ptrname/ptrcontent section */
|
|
curl_formadd(&post, &last, CURLFORM_PTRNAME, namebuffer,
|
|
CURLFORM_PTRCONTENTS, buffer, CURLFORM_NAMELENGTH,
|
|
namelength, CURLFORM_END);
|
|
|
|
/* Add name/ptrcontent/contenttype section */
|
|
curl_formadd(&post, &last, CURLFORM_COPYNAME, "html_code_with_hole",
|
|
CURLFORM_PTRCONTENTS, htmlbuffer,
|
|
CURLFORM_CONTENTSLENGTH, htmlbufferlength,
|
|
CURLFORM_CONTENTTYPE, "text/html", CURLFORM_END);
|
|
|
|
/* Add simple file section */
|
|
curl_formadd(&post, &last, CURLFORM_COPYNAME, "picture",
|
|
CURLFORM_FILE, "my-face.jpg", CURLFORM_END);
|
|
|
|
/* Add file/contenttype section */
|
|
curl_formadd(&post, &last, CURLFORM_COPYNAME, "picture",
|
|
CURLFORM_FILE, "my-face.jpg",
|
|
CURLFORM_CONTENTTYPE, "image/jpeg", CURLFORM_END);
|
|
|
|
/* Add two file section */
|
|
curl_formadd(&post, &last, CURLFORM_COPYNAME, "pictures",
|
|
CURLFORM_FILE, "my-face.jpg",
|
|
CURLFORM_FILE, "your-face.jpg", CURLFORM_END);
|
|
|
|
/* Add two file section using CURLFORM_ARRAY */
|
|
forms[0].option = CURLFORM_FILE;
|
|
forms[0].value = file1;
|
|
forms[1].option = CURLFORM_FILE;
|
|
forms[1].value = file2;
|
|
forms[2].option = CURLFORM_END;
|
|
|
|
/* Add a buffer to upload */
|
|
curl_formadd(&post, &last,
|
|
CURLFORM_COPYNAME, "name",
|
|
CURLFORM_BUFFER, "data",
|
|
CURLFORM_BUFFERPTR, record,
|
|
CURLFORM_BUFFERLENGTH, record_length,
|
|
CURLFORM_END);
|
|
|
|
/* no option needed for the end marker */
|
|
curl_formadd(&post, &last, CURLFORM_COPYNAME, "pictures",
|
|
CURLFORM_ARRAY, forms, CURLFORM_END);
|
|
/* Add the content of a file as a normal post text value */
|
|
curl_formadd(&post, &last, CURLFORM_COPYNAME, "filecontent",
|
|
CURLFORM_FILECONTENT, ".bashrc", CURLFORM_END);
|
|
/* Set the form info */
|
|
curl_easy_setopt(curl, CURLOPT_HTTPPOST, post);
|
|
|
|
|
|
|
|
</PRE>
|
|
<H2>SEE ALSO</H2><PRE>
|
|
|
|
|
|
</PRE>
|
|
<H2>BUGS</H2><PRE>
|
|
Surely there are some, you tell me!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
<HR>
|
|
<ADDRESS>
|
|
Man(1) output converted with
|
|
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|