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 /tests/data/test1012 | |
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 'tests/data/test1012')
-rw-r--r-- | tests/data/test1012 | 79 |
1 files changed, 79 insertions, 0 deletions
diff --git a/tests/data/test1012 b/tests/data/test1012 new file mode 100644 index 000000000..6aa17156d --- /dev/null +++ b/tests/data/test1012 @@ -0,0 +1,79 @@ +<testcase> +<info> +<keywords> +HTTP +HTTP POST +followlocation +</keywords> +</info> +# +# Server-side +<reply> +<data> +HTTP/1.1 301 OK swsclose
+Location: moo.html&testcase=/10120002
+Date: Thu, 09 Nov 2010 14:49:00 GMT
+Connection: close
+
+</data> +<data2> +HTTP/1.1 200 OK swsclose +Location: this should be ignored +Date: Thu, 09 Nov 2010 14:49:00 GMT +Connection: close + +body +</data2> +<datacheck> +HTTP/1.1 301 OK swsclose
+Location: moo.html&testcase=/10120002
+Date: Thu, 09 Nov 2010 14:49:00 GMT
+Connection: close
+
+HTTP/1.1 200 OK swsclose +Location: this should be ignored +Date: Thu, 09 Nov 2010 14:49:00 GMT +Connection: close + +body +</datacheck> +</reply> + +# +# Client-side +<client> +<server> +http +</server> + <name> +HTTP POST with 301 redirect and --post301 + </name> + <command> +http://%HOSTIP:%HTTPPORT/blah/1012 -L -d "moo" --post301 +</command> +</client> + +# +# Verify data after the test has been "shot" +<verify> +<strip> +^User-Agent:.* +</strip> +<protocol nonewline="yes"> +POST /blah/1012 HTTP/1.1
+Host: %HOSTIP:%HTTPPORT
+Accept: */*
+Content-Length: 3
+Content-Type: application/x-www-form-urlencoded
+
+mooPOST /blah/moo.html&testcase=/10120002 HTTP/1.1
+User-Agent: curl/7.10 (i686-pc-linux-gnu) libcurl/7.10 OpenSSL/0.9.6c ipv6 zlib/1.1.3
+Host: %HOSTIP:%HTTPPORT
+Accept: */*
+Content-Length: 3
+Content-Type: application/x-www-form-urlencoded
+
+moo +</protocol> +</verify> +</testcase> |