moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-08 18:45:05 -05:00
Code Issues Releases Wiki Activity
b735717606
curl/tests/data/test11

77 lines
1.3 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
followlocation
</keywords>
</info>
test case converted to the new file format
2001-05-28 08:30:21 -04:00
# Server-side
<reply>
<data>
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
HTTP/1.1 301 This is a weirdo text message swsclose
test case converted to the new file format
2001-05-28 08:30:21 -04:00
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Location: data/110002.txt?coolsite=yes
Connection: close
This server reply is for testing a simple Location: following
</data>
<data2>
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
HTTP/1.1 200 Followed here fine swsclose
test case converted to the new file format
2001-05-28 08:30:21 -04:00
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring.
2006-11-25 08:32:04 -05:00
Content-Length: 52
test case converted to the new file format
2001-05-28 08:30:21 -04:00
If this is received, the location following worked
</data2>
<datacheck>
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
HTTP/1.1 301 This is a weirdo text message swsclose
test case converted to the new file format
2001-05-28 08:30:21 -04:00
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Location: data/110002.txt?coolsite=yes
Connection: close
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
HTTP/1.1 200 Followed here fine swsclose
test case converted to the new file format
2001-05-28 08:30:21 -04:00
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring.
2006-11-25 08:32:04 -05:00
Content-Length: 52
test case converted to the new file format
2001-05-28 08:30:21 -04:00
If this is received, the location following worked
</datacheck>
</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>
test case converted to the new file format
2001-05-28 08:30:21 -04:00
<name>
simple HTTP Location: following
</name>
<command>
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script.
2004-09-08 04:08:38 -04:00
http://%HOSTIP:%HTTPPORT/want/11 -L
test case converted to the new file format
2001-05-28 08:30:21 -04:00
</command>
A minor "syntax error" in numerous test files corrected
2005-01-25 16:45:03 -05:00
</client>
test case converted to the new file format
2001-05-28 08:30:21 -04:00
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /want/11 HTTP/1.1
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 15:32:31 -04:00
Host: %HOSTIP:%HTTPPORT
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 07:46:41 -05:00
Accept: */*
test case converted to the new file format
2001-05-28 08:30:21 -04:00
GET /want/data/110002.txt?coolsite=yes HTTP/1.1
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 15:32:31 -04:00
Host: %HOSTIP:%HTTPPORT
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 07:46:41 -05:00
Accept: */*
test case converted to the new file format
2001-05-28 08:30:21 -04:00
</protocol>
</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