summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2008-09-05 16:13:20 +0000
committerDaniel Stenberg <daniel@haxx.se>2008-09-05 16:13:20 +0000
commit18110b519c56a464bca4258332279c580f07a52f (patch)
tree0818c63153e939254958ebeacce23ac713bd9bba /docs
parent4c9768565ec3a9baf26ac8a547bca6e42cc64fa5 (diff)
downloadcurl-18110b519c56a464bca4258332279c580f07a52f.tar.gz
- Martin Drasar provided the CURLOPT_POSTREDIR patch. It renames
CURLOPT_POST301 (but adds a define for backwards compatibility for you who don't define CURL_NO_OLDIES). This option allows you to now also change the libcurl behavior for a HTTP response 302 after a POST to not use GET in the subsequent request (when CURLOPT_FOLLOWLOCATION is enabled). I edited the patch somewhat before commit. The curl tool got a matching --post302 option. Test case 1076 was added to verify this.
Diffstat (limited to 'docs')
-rw-r--r--docs/curl.17
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/curl.1 b/docs/curl.1
index 57cb79dde..0ce5c9fbf 100644
--- a/docs/curl.1
+++ b/docs/curl.1
@@ -870,6 +870,13 @@ in web browsers, so curl 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 using \fI-L/--location\fP
(Added in 7.17.1)
+.IP "--post302"
+Tells curl to respect RFC 2616/10.3.2 and not convert POST requests into GET
+requests when following a 302 redirection. The non-RFC behaviour is ubiquitous
+in web browsers, so curl 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 using \fI-L/--location\fP
+(Added in 7.19.1)
.IP "--proxy-anyauth"
Tells curl to pick a suitable authentication method when communicating with
the given proxy. This might cause an extra request/response round-trip. (Added