diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2007-09-26 12:44:59 +0000 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2007-09-26 12:44:59 +0000 |
| commit | fd4cf78f36e89b8a0913e4fb34fd7a89f5c0cfd4 (patch) | |
| tree | c4a2dfb16d9985c715a6f4b2a6dfbe7edd2dc1c4 /lib | |
| parent | a6315359d742bdf967ba3ee1db3e0b7e5a3956fe (diff) | |
Philip Langdale provided the new CURLOPT_POST301 option for
curl_easy_setopt() that alters how libcurl functions when following
redirects. It makes libcurl obey the RFC2616 when a 301 response is received
after a non-GET request is made. Default libcurl behaviour is to change
method to GET in the subsequent request (like it does for response code 302
- because that's what many/most browsers do), but with this CURLOPT_POST301
option enabled it will do what the spec says and do the next request using
the same method again. I.e keep POST after 301.
The curl tool got this option as --post301
Test case 1011 and 1012 were added to verify.
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/transfer.c | 9 | ||||
| -rw-r--r-- | lib/url.c | 7 | ||||
| -rw-r--r-- | lib/urldata.h | 1 |
3 files changed, 14 insertions, 3 deletions
diff --git a/lib/transfer.c b/lib/transfer.c index d16d29268..29e53690b 100644 --- a/lib/transfer.c +++ b/lib/transfer.c @@ -2257,10 +2257,13 @@ CURLcode Curl_follow(struct SessionHandle *data, * violation, many webservers expect this misbehavior. So these servers * often answers to a POST request with an error page. To be sure that * libcurl gets the page that most user agents would get, libcurl has to - * force GET: + * force GET. + * + * This behaviour can be overriden with CURLOPT_POST301. */ - if( data->set.httpreq == HTTPREQ_POST - || data->set.httpreq == HTTPREQ_POST_FORM) { + if( (data->set.httpreq == HTTPREQ_POST + || data->set.httpreq == HTTPREQ_POST_FORM) + && !data->set.post301) { infof(data, "Violate RFC 2616/10.3.2 and switch from POST to GET\n"); data->set.httpreq = HTTPREQ_GET; @@ -924,6 +924,13 @@ CURLcode Curl_setopt(struct SessionHandle *data, CURLoption option, data->set.maxredirs = va_arg(param, long); break; + case CURLOPT_POST301: + /* + * Obey RFC 2616/10.3.2 and resubmit a POST as a POST after a 301. + */ + data->set.post301 = (bool)(0 != va_arg(param, long)); + break; + case CURLOPT_POST: /* Does this option serve a purpose anymore? Yes it does, when CURLOPT_POSTFIELDS isn't used and the POST data is read off the diff --git a/lib/urldata.h b/lib/urldata.h index 435693ee0..b1de21ac5 100644 --- a/lib/urldata.h +++ b/lib/urldata.h @@ -1306,6 +1306,7 @@ struct UserDefined { long followlocation; /* as in HTTP Location: */ long maxredirs; /* maximum no. of http(s) redirects to follow, set to -1 for infinity */ + bool post301; /* Obey RFC 2616/10.3.2 and keep POSTs as POSTs after a 301 */ bool free_referer; /* set TRUE if 'referer' points to a string we allocated */ curl_off_t postfieldsize; /* if POST, this might have a size to use instead |