From 1d12b1fa1e260c14d55b1620cf4e251d16f3d6b6 Mon Sep 17 00:00:00 2001 From: Dan Fandrich Date: Thu, 16 Oct 2008 21:02:38 +0000 Subject: CURLOPT_POST301 => CURLOPT_POSTREDIR --- docs/libcurl/curl_easy_setopt.3 | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index 9759e8fcc..31482a168 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -21,7 +21,7 @@ .\" * $Id$ .\" ************************************************************************** .\" -.TH curl_easy_setopt 3 "30 Jul 2008" "libcurl 7.19.0" "libcurl Manual" +.TH curl_easy_setopt 3 "16 Oct 2008" "libcurl 7.19.1" "libcurl Manual" .SH NAME curl_easy_setopt \- set options for a curl easy handle .SH SYNOPSIS @@ -729,13 +729,14 @@ redirections have been followed, the next redirect will cause an error \fICURLOPT_FOLLOWLOCATION\fP is used at the same time. Added in 7.15.1: Setting the limit to 0 will make libcurl refuse any redirect. Set it to -1 for an infinite number of redirects (which is the default) -.IP CURLOPT_POST301 +.IP CURLOPT_POSTREDIR A parameter set to 1 tells the library to respect RFC 2616/10.3.2 and not convert POST requests into GET requests when following a 301 redirection. The non-RFC behaviour is ubiquitous in web browsers, so the library does the conversion by default to maintain consistency. However, a server may requires a POST to remain a POST after such a redirection. This option is meaningful only when setting \fICURLOPT_FOLLOWLOCATION\fP. (Added in 7.17.1) +(This option was known as CURLOPT_POST301 up to 7.19.0) .IP CURLOPT_PUT A parameter set to 1 tells the library to use HTTP PUT to transfer data. The data should be set with \fICURLOPT_READDATA\fP and \fICURLOPT_INFILESIZE\fP. -- cgit v1.2.3