moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-14 05:25:06 -05:00
Code Issues Releases Wiki Activity
7098f9fe3a
curl/tests/data/test18

89 lines
1.2 KiB
Plaintext
Raw Normal View History

Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools.
2007-01-22 21:25:56 -05:00
<testcase>
keywords added
2005-04-16 19:15:19 -04:00
<info>
<keywords>
HTTP
HTTP GET
tests: added globbing keyword to URL globbing tests
2014-07-11 19:49:35 -04:00
globbing
keywords added
2005-04-16 19:15:19 -04:00
{} list
</keywords>
</info>
nine new test cases
2001-08-07 08:42:23 -04:00
# Server-side
<reply>
Always use nocheck="yes" for consistency
2009-01-07 16:57:26 -05:00
<data nocheck="yes">
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
HTTP/1.1 200 OK
Funny-head: yesyes
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
Content-Length: 4
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
nine new test cases
2001-08-07 08:42:23 -04:00
moo
</data>
<data2>
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
HTTP/1.1 200 OK
Funny-head: yesyes
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
Content-Length: 4
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
nine new test cases
2001-08-07 08:42:23 -04:00
foo
</data2>
<data3>
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
HTTP/1.1 200 OK
Funny-head: yesyes
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
Content-Length: 4
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
nine new test cases
2001-08-07 08:42:23 -04:00
hoo
</data3>
</reply>
# Client-side
<client>
Each test case now specifies which server(s) it needs, without relying on the test number.
2003-04-30 16:25:39 -04:00
<server>
http
</server>
nine new test cases
2001-08-07 08:42:23 -04:00
<name>
multiple requests using {} in URL
</name>
<command>
Use double quotes in command lines for consistency.
2007-09-18 16:41:20 -04:00
"%HOSTIP:%HTTPPORT/{18,180002,180003}"
nine new test cases
2001-08-07 08:42:23 -04:00
</command>
A minor "syntax error" in numerous test files corrected
2005-01-25 16:45:03 -05:00
</client>
nine new test cases
2001-08-07 08:42:23 -04:00
# Verify data after the test has been "shot"
<verify>
<protocol>
GET /18 HTTP/1.1
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 15:32:31 -04:00
Host: %HOSTIP:%HTTPPORT
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037
2020-10-02 07:45:24 -04:00
User-Agent: curl/%VERSION
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 07:46:41 -05:00
Accept: */*
nine new test cases
2001-08-07 08:42:23 -04:00
GET /180002 HTTP/1.1
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 15:32:31 -04:00
Host: %HOSTIP:%HTTPPORT
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037
2020-10-02 07:45:24 -04:00
User-Agent: curl/%VERSION
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 07:46:41 -05:00
Accept: */*
nine new test cases
2001-08-07 08:42:23 -04:00
GET /180003 HTTP/1.1
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 15:32:31 -04:00
Host: %HOSTIP:%HTTPPORT
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037
2020-10-02 07:45:24 -04:00
User-Agent: curl/%VERSION
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 07:46:41 -05:00
Accept: */*
nine new test cases
2001-08-07 08:42:23 -04:00
</protocol>
<stdout>
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 15:32:31 -04:00
--_curl_--%HOSTIP:%HTTPPORT/18
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
HTTP/1.1 200 OK
Funny-head: yesyes
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
Content-Length: 4
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
nine new test cases
2001-08-07 08:42:23 -04:00
moo
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 15:32:31 -04:00
--_curl_--%HOSTIP:%HTTPPORT/180002
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
HTTP/1.1 200 OK
Funny-head: yesyes
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
Content-Length: 4
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
nine new test cases
2001-08-07 08:42:23 -04:00
foo
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 15:32:31 -04:00
--_curl_--%HOSTIP:%HTTPPORT/180003
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
HTTP/1.1 200 OK
Funny-head: yesyes
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
Content-Length: 4
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
nine new test cases
2001-08-07 08:42:23 -04:00
hoo
</stdout>
</verify>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => &amp; ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools.
2007-01-22 21:25:56 -05:00
</testcase>
Reference in New Issue Copy Permalink