From: Daniel Stenberg <daniel@haxx.se>
Date: Sun, 22 Apr 2007 08:05:40 +0000 (+0000)
Subject: clarify a bit on the follow-redirect logic and when curl switches from POST
X-Git-Tag: curl-7_16_3~158
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=56a5c49ac085a6a1abfa7799f722c15bf94112f6;p=thirdparty%2Fcurl.git

clarify a bit on the follow-redirect logic and when curl switches from POST
to GET on redirect
---

diff --git a/docs/curl.1 b/docs/curl.1
index 3014613395..dd5d1d7588 100644
--- a/docs/curl.1
+++ b/docs/curl.1
@@ -704,6 +704,11 @@ able to intercept the user+password. See also \fI--location-trusted\fP on how
 to change this. You can limit the amount of redirects to follow by using the
 \fI--max-redirs\fP option.
 
+When curl follows a redirect and the request is not a plain GET (for example
+POST or PUT), it will do the following request with a GET if the HTTP response
+was 301, 302, or 303. If the response code was any other 3xx code, curl will
+re-send the following request using the same unmodified method.
+
 If this option is used twice, the second will again disable location following.
 .IP "--location-trusted"
 (HTTP/HTTPS) Like \fI-L/--location\fP, but will allow sending the name +