moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-12-23 08:38:49 -05:00
Code Issues Releases Wiki Activity
c8a47bf662
curl/tests/data/test506

171 lines
4.5 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>
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
# Server-side
<reply>
<data1>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Content-Type: text/html
Year 2038 has its own problems (32 bit integer overflow). So cookie expiration date is lowered to expire at most in 2035.
2007-02-04 21:38:25 -05:00
Set-Cookie: test1=one; domain=foo.com; expires=Sat Feb 2 11:56:27 GMT 2030
Set-Cookie: test2=two; domain=host.foo.com; expires=Sat Feb 2 11:56:27 GMT 2030
Set-Cookie: test3=three; domain=foo.com; expires=Sat Feb 2 11:56:27 GMT 2030
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
Content-Length: 29
run 1: set cookie 1, 2 and 3
</data1>
<data2>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:01 GMT
Server: test-server/fake
Content-Type: text/html
Year 2038 has its own problems (32 bit integer overflow). So cookie expiration date is lowered to expire at most in 2035.
2007-02-04 21:38:25 -05:00
Set-Cookie: test4=four; domain=host.foo.com; expires=Sat Feb 2 11:56:27 GMT 2030
Set-Cookie: test5=five; domain=host.foo.com; expires=Sat Feb 2 11:56:27 GMT 2030
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
Content-Length: 26
run 2: set cookie 4 and 5
</data2>
<data3>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:02 GMT
Server: test-server/fake
Content-Type: text/html
Funny-head: yesyes
Year 2038 has its own problems (32 bit integer overflow). So cookie expiration date is lowered to expire at most in 2035.
2007-02-04 21:38:25 -05:00
Set-Cookie: test4=overwritten4; domain=host.foo.com; expires=Sat May 5 GMT 11:56:27 2035
Set-Cookie: test1=overwritten1; domain=foo.com; expires=Thu Mar 3 GMT 11:56:27 2033
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
Content-Type: text/html
Content-Length: 32
run 3: overwrite cookie 1 and 4
Andres Garcia's text mode fix for the 'data' part
2005-06-03 10:06:03 -04:00
</data3>
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
</reply>
# Client-side
<client>
<server>
http
</server>
<name>
HTTP with shared cookie list (and dns cache)
</name>
<tool>
lib506
</tool>
<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/506
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
</command>
</client>
# Verify data after the test has been "shot"
<verify>
Andres Garcia's text mode fix for the 'data' part
2005-06-03 10:06:03 -04:00
<stdout mode="text">
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
GLOBAL_INIT
SHARE_INIT
tests/libtest/lib506.c version 1.11 is now also logging CURLSHOPT_LOCKFUNC, CURLSHOPT_UNLOCKFUNC and CURLSHOPT_USERDATA, so we now also have to check them here.
2006-07-17 12:47:07 -04:00
CURLSHOPT_LOCKFUNC
CURLSHOPT_UNLOCKFUNC
CURLSHOPT_USERDATA
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
CURL_LOCK_DATA_COOKIE
CURL_LOCK_DATA_DNS
*** run 1
CURLOPT_SHARE
modified and corrected test 506
2003-12-16 04:49:36 -05:00
lock: share <Pigs in space>: 0
unlock: share <Pigs in space>: 1
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
PERFORM
modified and corrected test 506
2003-12-16 04:49:36 -05:00
lock: dns <Pigs in space>: 2
unlock: dns <Pigs in space>: 3
lock: dns <Pigs in space>: 4
unlock: dns <Pigs in space>: 5
lock: cookie <Pigs in space>: 6
unlock: cookie <Pigs in space>: 7
lock: cookie <Pigs in space>: 8
unlock: cookie <Pigs in space>: 9
lock: cookie <Pigs in space>: 10
unlock: cookie <Pigs in space>: 11
lock: cookie <Pigs in space>: 12
unlock: cookie <Pigs in space>: 13
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
run 1: set cookie 1, 2 and 3
modified and corrected test 506
2003-12-16 04:49:36 -05:00
lock: dns <Pigs in space>: 14
unlock: dns <Pigs in space>: 15
adjusted to the moved unlock of the DNS entry
2005-01-28 17:22:59 -05:00
CLEANUP
modified and corrected test 506
2003-12-16 04:49:36 -05:00
lock: dns <Pigs in space>: 16
unlock: dns <Pigs in space>: 17
lock: cookie <Pigs in space>: 18
unlock: cookie <Pigs in space>: 19
lock: share <Pigs in space>: 20
unlock: share <Pigs in space>: 21
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
*** run 2
CURLOPT_SHARE
lock: share <Pigs in space>: 22
unlock: share <Pigs in space>: 23
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
PERFORM
Made the dns entry remain locked while a connection to the host remains to allow verbose output during this period. Bertrand Demiddelaer reported and helped fixing.
2004-10-04 06:36:51 -04:00
lock: dns <Pigs in space>: 24
unlock: dns <Pigs in space>: 25
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
lock: dns <Pigs in space>: 26
unlock: dns <Pigs in space>: 27
modified and corrected test 506
2003-12-16 04:49:36 -05:00
lock: cookie <Pigs in space>: 28
unlock: cookie <Pigs in space>: 29
Made the dns entry remain locked while a connection to the host remains to allow verbose output during this period. Bertrand Demiddelaer reported and helped fixing.
2004-10-04 06:36:51 -04:00
lock: cookie <Pigs in space>: 30
unlock: cookie <Pigs in space>: 31
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
lock: cookie <Pigs in space>: 32
unlock: cookie <Pigs in space>: 33
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
run 2: set cookie 4 and 5
Made the dns entry remain locked while a connection to the host remains to allow verbose output during this period. Bertrand Demiddelaer reported and helped fixing.
2004-10-04 06:36:51 -04:00
lock: dns <Pigs in space>: 34
unlock: dns <Pigs in space>: 35
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
CLEANUP
lock: dns <Pigs in space>: 36
unlock: dns <Pigs in space>: 37
lock: cookie <Pigs in space>: 38
unlock: cookie <Pigs in space>: 39
lock: share <Pigs in space>: 40
unlock: share <Pigs in space>: 41
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
*** run 3
CURLOPT_SHARE
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
lock: share <Pigs in space>: 42
unlock: share <Pigs in space>: 43
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
CURLOPT_COOKIEJAR
PERFORM
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
lock: dns <Pigs in space>: 44
unlock: dns <Pigs in space>: 45
lock: dns <Pigs in space>: 46
unlock: dns <Pigs in space>: 47
Made the dns entry remain locked while a connection to the host remains to allow verbose output during this period. Bertrand Demiddelaer reported and helped fixing.
2004-10-04 06:36:51 -04:00
lock: cookie <Pigs in space>: 48
unlock: cookie <Pigs in space>: 49
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
lock: cookie <Pigs in space>: 50
unlock: cookie <Pigs in space>: 51
lock: cookie <Pigs in space>: 52
unlock: cookie <Pigs in space>: 53
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
run 3: overwrite cookie 1 and 4
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
lock: dns <Pigs in space>: 54
unlock: dns <Pigs in space>: 55
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
try SHARE_CLEANUP...
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
lock: share <Pigs in space>: 56
unlock: share <Pigs in space>: 57
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
SHARE_CLEANUP failed, correct
CLEANUP
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
lock: dns <Pigs in space>: 58
unlock: dns <Pigs in space>: 59
lock: cookie <Pigs in space>: 60
unlock: cookie <Pigs in space>: 61
lock: share <Pigs in space>: 62
unlock: share <Pigs in space>: 63
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
SHARE_CLEANUP
Gerrit Bruchhäuser pointed out a warning that the Intel(R) Thread Checker tool reports and it was indeed a legitimate one and it is one fixed. It was a use of a share without doing the proper locking first.
2007-06-21 10:23:38 -04:00
lock: share <Pigs in space>: 64
unlock: share <Pigs in space>: 65
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
GLOBAL_CLEANUP
</stdout>
<stderr>
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/506
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
</stderr>
Andres Garcia's text mode fix for the 'data' part
2005-06-03 10:06:03 -04:00
<file name="log/jar506" mode="text">
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
# Netscape HTTP Cookie File
As reported in bug: #1566077 the former URL mentioned in the generated cookie jar has died and we now instead point out our own version of that
2006-09-27 17:00:45 -04:00
# http://curlm.haxx.se/rfc/cookie_spec.html
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
# This file was generated by libcurl! Edit at your own risk.
Year 2038 has its own problems (32 bit integer overflow). So cookie expiration date is lowered to expire at most in 2035.
2007-02-04 21:38:25 -05:00
.foo.com TRUE / FALSE 1993463787 test1 overwritten1
.host.foo.com TRUE / FALSE 1896263787 test2 two
.foo.com TRUE / FALSE 1896263787 test3 three
.host.foo.com TRUE / FALSE 2061978987 test4 overwritten4
.host.foo.com TRUE / FALSE 1896263787 test5 five
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
</file>
</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