mirror/curl
2
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2024-12-15 06:40:09 +08:00
Code Issues Packages Projects Releases Wiki Activity
cb2ae6e8a8
curl/tests/data/test1188

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

57 lines
1002 B
Plaintext
Raw Normal View History

test: verify new --write-out variables Extended test 1029 and added 1188
2020-12-21 06:00:13 +08:00
<testcase>
<info>
<keywords>
HTTP
HTTP GET
--write-out
</keywords>
</info>
# Server-side
<reply>
test1188: Check for --fail HTTP status - Change the test to check for curl error on HTTP 404 Not Found. test1188 tests "--write-out with %{onerror} and %{urlnum} to stderr". Prior to this change it did that by specifying a non-existent host which would cause an error. ISPs may hijack DNS and resolve non-existent hosts so the test would not work if that was the case. Ref: https://en.wikipedia.org/wiki/DNS_hijacking#Manipulation_by_ISPs Ref: https://github.com/curl/curl/issues/6621 Ref: https://github.com/curl/curl/pull/6623 Closes https://github.com/curl/curl/pull/6637
2021-02-20 07:30:18 +08:00
<data>
HTTP/1.1 404 Not Found
Content-Length: 0
test: verify new --write-out variables Extended test 1029 and added 1188
2020-12-21 06:00:13 +08:00
Connection: close
</data>
</reply>
# Client-side
<client>
<server>
http
</server>
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028
2023-10-04 17:35:54 +08:00
<name>
test: verify new --write-out variables Extended test 1029 and added 1188
2020-12-21 06:00:13 +08:00
--write-out with %{onerror} and %{urlnum} to stderr
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028
2023-10-04 17:35:54 +08:00
</name>
test: verify new --write-out variables Extended test 1029 and added 1188
2020-12-21 06:00:13 +08:00
<command>
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738
2021-03-13 00:38:26 +08:00
-f -s -w '%{onerror}%{stderr}%{urlnum} says %{exitcode} %{errormsg}\n' http://%HOSTIP:%HTTPPORT/we/want/our/%TESTNUMBER http://%HOSTIP:%HTTPPORT/we/want/our/%TESTNUMBER
test: verify new --write-out variables Extended test 1029 and added 1188
2020-12-21 06:00:13 +08:00
</command>
</client>
# Verify data after the test has been "shot"
<verify>
<protocol>
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738
2021-03-13 00:38:26 +08:00
GET /we/want/our/%TESTNUMBER HTTP/1.1
test: verify new --write-out variables Extended test 1029 and added 1188
2020-12-21 06:00:13 +08:00
Host: %HOSTIP:%HTTPPORT
User-Agent: curl/%VERSION
Accept: */*
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738
2021-03-13 00:38:26 +08:00
GET /we/want/our/%TESTNUMBER HTTP/1.1
test1188: Check for --fail HTTP status - Change the test to check for curl error on HTTP 404 Not Found. test1188 tests "--write-out with %{onerror} and %{urlnum} to stderr". Prior to this change it did that by specifying a non-existent host which would cause an error. ISPs may hijack DNS and resolve non-existent hosts so the test would not work if that was the case. Ref: https://en.wikipedia.org/wiki/DNS_hijacking#Manipulation_by_ISPs Ref: https://github.com/curl/curl/issues/6621 Ref: https://github.com/curl/curl/pull/6623 Closes https://github.com/curl/curl/pull/6637
2021-02-20 07:30:18 +08:00
Host: %HOSTIP:%HTTPPORT
User-Agent: curl/%VERSION
Accept: */*
test: verify new --write-out variables Extended test 1029 and added 1188
2020-12-21 06:00:13 +08:00
</protocol>
<stderr mode="text">
test1188: Check for --fail HTTP status - Change the test to check for curl error on HTTP 404 Not Found. test1188 tests "--write-out with %{onerror} and %{urlnum} to stderr". Prior to this change it did that by specifying a non-existent host which would cause an error. ISPs may hijack DNS and resolve non-existent hosts so the test would not work if that was the case. Ref: https://en.wikipedia.org/wiki/DNS_hijacking#Manipulation_by_ISPs Ref: https://github.com/curl/curl/issues/6621 Ref: https://github.com/curl/curl/pull/6623 Closes https://github.com/curl/curl/pull/6637
2021-02-20 07:30:18 +08:00
0 says 22 The requested URL returned error: 404
1 says 22 The requested URL returned error: 404
test: verify new --write-out variables Extended test 1029 and added 1188
2020-12-21 06:00:13 +08:00
</stderr>
test1188: Check for --fail HTTP status - Change the test to check for curl error on HTTP 404 Not Found. test1188 tests "--write-out with %{onerror} and %{urlnum} to stderr". Prior to this change it did that by specifying a non-existent host which would cause an error. ISPs may hijack DNS and resolve non-existent hosts so the test would not work if that was the case. Ref: https://en.wikipedia.org/wiki/DNS_hijacking#Manipulation_by_ISPs Ref: https://github.com/curl/curl/issues/6621 Ref: https://github.com/curl/curl/pull/6623 Closes https://github.com/curl/curl/pull/6637
2021-02-20 07:30:18 +08:00
# 22 is CURLE_HTTP_RETURNED_ERROR
<errorcode>
22
</errorcode>
test: verify new --write-out variables Extended test 1029 and added 1188
2020-12-21 06:00:13 +08:00
</verify>
</testcase>
Reference in New Issue Copy Permalink