Does this look more sane?:

Index: src/vendor/curl/docs/libcurl/opts/CURLOPT_POSTFIELDS.3
==================================================================
--- src/vendor/curl/docs/libcurl/opts/CURLOPT_POSTFIELDS.3
+++ src/vendor/curl/docs/libcurl/opts/CURLOPT_POSTFIELDS.3
@@ -33,10 +33,12 @@
 server to receive it. libcurl will not convert or encode it for you in any
 way. For example, the web server may assume that this data is url-encoded.

 The data pointed to is NOT copied by the library: as a consequence, it must be
 preserved by the calling application until the associated transfer finishes.
+This behaviour can be changed (so libcurl does copy the data) by setting the
+CURLOPT_COPYPOSTFIELDS option.

 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 commonly
 used by HTML forms. Change Content-Type with \fICURLOPT_HTTPHEADER(3)\fP.

@@ -77,6 +79,6 @@
 .SH AVAILABILITY
 Always
 .SH RETURN VALUE
 Returns CURLE_OK
 .SH "SEE ALSO"
-.BR CURLOPT_POSTFIELDSIZE "(3), " CURLOPT_READFUNCTION "(3), "
+.BR CURLOPT_POSTFIELDSIZE "(3), " CURLOPT_READFUNCTION "(3), "
CURLOPT_COPYPOSTFIELDS "(3)"

On 11/19/14, Daniel Stenberg <daniel_at_haxx.se> wrote:
> On Tue, 18 Nov 2014, Dan Fandrich wrote:
>
>> or adding a sentence at the end of this paragraph suggesting that
>> CURLOPT_COPYPOSTFIELDS is a way around this limitation.
>
> Yeah, that'd be my preference. Making sure that the alternative that
> actually
> DOES copy is conveyed properly.
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-11-19