From 14d6e207d35792e3e10a674b2e27cf2aa3370bf8 Mon Sep 17 00:00:00 2001 From: Patrick Monnerat Date: Sun, 8 Oct 2017 16:15:23 +0100 Subject: docs: clarify form/mime usage of non-regular data files. --- docs/libcurl/curl_mime_filedata.3 | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'docs/libcurl/curl_mime_filedata.3') diff --git a/docs/libcurl/curl_mime_filedata.3 b/docs/libcurl/curl_mime_filedata.3 index 9a57068de..f522d997f 100644 --- a/docs/libcurl/curl_mime_filedata.3 +++ b/docs/libcurl/curl_mime_filedata.3 @@ -36,7 +36,7 @@ data to a mime part. \fIpart\fP is the part's to assign contents to. \fIfilename\fP points to the nul-terminated file's path name. The pointer can -be NULL to detach previous part contents settings. Filename storage can be +be NULL to detach the previous part contents settings. Filename storage can be safely be reused after this call. As a side effect, the part's remote file name is set to the base name of the @@ -47,6 +47,10 @@ The contents of the file is read during the file transfer in a streaming manner to allow huge files to get transfered without using much memory. It therefore requires that the file is kept intact during the entire request. +If the file size cannot be determined before actually reading it (such as for +a device or named pipe), the whole mime structure containing the part +will be transferred as chunks by HTTP and rejected by IMAP. + Setting a part's contents twice is valid: only the value set by the last call is retained. .SH AVAILABILITY -- cgit v1.2.3