moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-16 06:25:03 -05:00
Code Issues Releases Wiki Activity
284d06df9e
curl/tests/data/test506

244 lines
6.9 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>
Added some <keywords> sections and use some key words more consistently.
2007-10-11 21:44:22 -04:00
<info>
<keywords>
HTTP
HTTP GET
cookies
shared cookies
</keywords>
</info>
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
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
Set-Cookie: test6=six; domain=.www.host.foo.com; expires=Thu Mar 3 GMT 11:56:27 2033
Set-Cookie: test6=six_more; 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
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
Content-Length: 73
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
run 3: overwrite cookie 1 and 4, set cookie 6 with and without tailmatch
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>
test506: skip if threaded-resolver
2017-07-06 05:11:43 -04:00
# don't run this with the threaded-resolver since the events might trigger in
# a different order!
<features>
!threaded-resolver
</features>
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
<name>
HTTP with shared cookie list (and dns cache)
</name>
Force the time zone to GMT in the cookie tests in case the user is using one of the so-called 'right' time zones that take into account leap seconds, which causes the tests to fail (as reported by Daniel Black in bug report #1745964).
2007-07-10 18:27:16 -04:00
# Explicitly set the time zone to a known good one, in case the user is
# using one of the 'right' zones that take into account leap seconds
# which causes the cookie expiry times to be different.
<setenv>
TZ=GMT
</setenv>
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
<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>
testsuite: use binary output mode for custom curl test tools Do not try to convert line-endings to CRLF on Windows by setting stdout to binary mode, just like the curl tool does if --ascii is not specified. This should prevent corrupted stdout line-ending output like CRCRLF. In order to make the previously naive text-aware tests work with binary mode on Windows, text-mode is disabled for them if it is not actually part of the test case and line-endings are corrected.
2014-01-31 18:58:58 -05:00
<stdout>
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
CURLOPT_SHARE
Changed the test data file so it passes an XML syntax check
2008-09-15 18:35:09 -04:00
lock: share [Pigs in space]: 0
unlock: share [Pigs in space]: 1
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
CURLOPT_COOKIELIST injected_and_clobbered
lock: cookie [Pigs in space]: 2
unlock: cookie [Pigs in space]: 3
CURLOPT_COOKIELIST ALL
lock: cookie [Pigs in space]: 4
unlock: cookie [Pigs in space]: 5
CURLOPT_COOKIELIST session
Changed the test data file so it passes an XML syntax check
2008-09-15 18:35:09 -04:00
lock: cookie [Pigs in space]: 6
unlock: cookie [Pigs in space]: 7
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
CURLOPT_COOKIELIST injected
Changed the test data file so it passes an XML syntax check
2008-09-15 18:35:09 -04:00
lock: cookie [Pigs in space]: 8
unlock: cookie [Pigs in space]: 9
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
CURLOPT_COOKIELIST SESS
Changed the test data file so it passes an XML syntax check
2008-09-15 18:35:09 -04:00
lock: cookie [Pigs in space]: 10
unlock: cookie [Pigs in space]: 11
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
CLEANUP
Changed the test data file so it passes an XML syntax check
2008-09-15 18:35:09 -04:00
lock: cookie [Pigs in space]: 12
unlock: cookie [Pigs in space]: 13
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
lock: share [Pigs in space]: 14
unlock: share [Pigs in space]: 15
*** run 1
Gerrit Bruchhuser 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
CURLOPT_SHARE
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
lock: share [Pigs in space]: 16
unlock: share [Pigs in space]: 17
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
PERFORM
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
lock: dns [Pigs in space]: 18
unlock: dns [Pigs in space]: 19
lock: dns [Pigs in space]: 20
unlock: dns [Pigs in space]: 21
lock: cookie [Pigs in space]: 22
unlock: cookie [Pigs in space]: 23
always-multi: always use non-blocking internals Remove internal separated behavior of the easy vs multi intercace. curl_easy_perform() is now using the multi interface itself. Several minor multi interface quirks and bugs have been fixed in the process. Much help with debugging this has been provided by: Yang Tse
2013-01-17 06:59:23 -05:00
lock: cookie [Pigs in space]: 24
unlock: cookie [Pigs in space]: 25
Changed the test data file so it passes an XML syntax check
2008-09-15 18:35:09 -04:00
lock: cookie [Pigs in space]: 26
unlock: cookie [Pigs in space]: 27
lock: cookie [Pigs in space]: 28
unlock: cookie [Pigs in space]: 29
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
run 1: set cookie 1, 2 and 3
always-multi: always use non-blocking internals Remove internal separated behavior of the easy vs multi intercace. curl_easy_perform() is now using the multi interface itself. Several minor multi interface quirks and bugs have been fixed in the process. Much help with debugging this has been provided by: Yang Tse
2013-01-17 06:59:23 -05:00
lock: dns [Pigs in space]: 30
unlock: dns [Pigs in space]: 31
updated according to the name resolve race condition fix just committed
2008-03-11 18:58:52 -04:00
CLEANUP
always-multi: always use non-blocking internals Remove internal separated behavior of the easy vs multi intercace. curl_easy_perform() is now using the multi interface itself. Several minor multi interface quirks and bugs have been fixed in the process. Much help with debugging this has been provided by: Yang Tse
2013-01-17 06:59:23 -05:00
lock: cookie [Pigs in space]: 32
unlock: cookie [Pigs in space]: 33
lock: share [Pigs in space]: 34
unlock: share [Pigs in space]: 35
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
*** run 2
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
CURLOPT_SHARE
always-multi: always use non-blocking internals Remove internal separated behavior of the easy vs multi intercace. curl_easy_perform() is now using the multi interface itself. Several minor multi interface quirks and bugs have been fixed in the process. Much help with debugging this has been provided by: Yang Tse
2013-01-17 06:59:23 -05:00
lock: share [Pigs in space]: 36
unlock: share [Pigs in space]: 37
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
PERFORM
always-multi: always use non-blocking internals Remove internal separated behavior of the easy vs multi intercace. curl_easy_perform() is now using the multi interface itself. Several minor multi interface quirks and bugs have been fixed in the process. Much help with debugging this has been provided by: Yang Tse
2013-01-17 06:59:23 -05:00
lock: dns [Pigs in space]: 38
unlock: dns [Pigs in space]: 39
lock: cookie [Pigs in space]: 40
unlock: cookie [Pigs in space]: 41
lock: cookie [Pigs in space]: 42
unlock: cookie [Pigs in space]: 43
Changed the test data file so it passes an XML syntax check
2008-09-15 18:35:09 -04:00
lock: cookie [Pigs in space]: 44
unlock: cookie [Pigs in space]: 45
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
run 2: set cookie 4 and 5
always-multi: always use non-blocking internals Remove internal separated behavior of the easy vs multi intercace. curl_easy_perform() is now using the multi interface itself. Several minor multi interface quirks and bugs have been fixed in the process. Much help with debugging this has been provided by: Yang Tse
2013-01-17 06:59:23 -05:00
lock: dns [Pigs in space]: 46
unlock: dns [Pigs in space]: 47
test case 506 added, written by Dirk Manske
2003-08-11 02:44:46 -04:00
CLEANUP
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
lock: cookie [Pigs in space]: 48
unlock: cookie [Pigs in space]: 49
lock: share [Pigs in space]: 50
unlock: share [Pigs in space]: 51
*** run 3
CURLOPT_SHARE
always-multi: always use non-blocking internals Remove internal separated behavior of the easy vs multi intercace. curl_easy_perform() is now using the multi interface itself. Several minor multi interface quirks and bugs have been fixed in the process. Much help with debugging this has been provided by: Yang Tse
2013-01-17 06:59:23 -05:00
lock: share [Pigs in space]: 52
unlock: share [Pigs in space]: 53
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
CURLOPT_COOKIEJAR
CURLOPT_COOKIELIST FLUSH
lock: cookie [Pigs in space]: 54
test506: verify aa6884845168 After the fixed cookie lock deadlock, this test now passes and it detects double-locking and double-unlocking of mutexes.
2014-07-15 18:09:58 -04:00
unlock: cookie [Pigs in space]: 55
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
PERFORM
test506: verify aa6884845168 After the fixed cookie lock deadlock, this test now passes and it detects double-locking and double-unlocking of mutexes.
2014-07-15 18:09:58 -04:00
lock: dns [Pigs in space]: 56
unlock: dns [Pigs in space]: 57
lock: cookie [Pigs in space]: 58
unlock: cookie [Pigs in space]: 59
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
lock: cookie [Pigs in space]: 60
unlock: cookie [Pigs in space]: 61
lock: cookie [Pigs in space]: 62
unlock: cookie [Pigs in space]: 63
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
lock: cookie [Pigs in space]: 64
unlock: cookie [Pigs in space]: 65
CURLOPT_COOKIELIST: Added "RELOAD" command
2014-09-25 10:25:52 -04:00
lock: cookie [Pigs in space]: 66
unlock: cookie [Pigs in space]: 67
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
run 3: overwrite cookie 1 and 4, set cookie 6 with and without tailmatch
lock: dns [Pigs in space]: 68
unlock: dns [Pigs in space]: 69
CLEANUP
lock: cookie [Pigs in space]: 70
unlock: cookie [Pigs in space]: 71
lock: share [Pigs in space]: 72
unlock: share [Pigs in space]: 73
CURLOPT_COOKIELIST: Added "RELOAD" command
2014-09-25 10:25:52 -04:00
CURLOPT_SHARE
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
lock: share [Pigs in space]: 74
unlock: share [Pigs in space]: 75
CURLOPT_COOKIELIST: Added "RELOAD" command
2014-09-25 10:25:52 -04:00
CURLOPT_COOKIELIST ALL
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
lock: cookie [Pigs in space]: 76
unlock: cookie [Pigs in space]: 77
CURLOPT_COOKIELIST: Added "RELOAD" command
2014-09-25 10:25:52 -04:00
CURLOPT_COOKIEJAR
CURLOPT_COOKIELIST RELOAD
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
lock: cookie [Pigs in space]: 78
unlock: cookie [Pigs in space]: 79
cookies: use lock when using CURLINFO_COOKIELIST Closes #1896
2017-09-18 18:50:16 -04:00
lock: cookie [Pigs in space]: 80
unlock: cookie [Pigs in space]: 81
CURLOPT_COOKIELIST: Added "RELOAD" command
2014-09-25 10:25:52 -04:00
loaded cookies:
-----------------
.host.foo.com TRUE / FALSE 1896263787 injected yes
.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
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
.www.host.foo.com TRUE / FALSE 1993463787 test6 six
www.host.foo.com FALSE / FALSE 1993463787 test6 six_more
CURLOPT_COOKIELIST: Added "RELOAD" command
2014-09-25 10:25:52 -04:00
-----------------
try SHARE_CLEANUP...
cookies: use lock when using CURLINFO_COOKIELIST Closes #1896
2017-09-18 18:50:16 -04:00
lock: share [Pigs in space]: 82
unlock: share [Pigs in space]: 83
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
SHARE_CLEANUP failed, correct
CLEANUP
cookies: use lock when using CURLINFO_COOKIELIST Closes #1896
2017-09-18 18:50:16 -04:00
lock: cookie [Pigs in space]: 84
unlock: cookie [Pigs in space]: 85
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
lock: share [Pigs in space]: 86
unlock: share [Pigs in space]: 87
cookies: use lock when using CURLINFO_COOKIELIST Closes #1896
2017-09-18 18:50:16 -04:00
SHARE_CLEANUP
lock: share [Pigs in space]: 88
unlock: share [Pigs in space]: 89
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
URLs: change all http:// URLs to https://
2016-02-02 18:19:02 -05:00
# https://curl.haxx.se/docs/http-cookies.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.
test506: verify that CURLOPT_COOKIELIST takes share lock It doesn't right now: http://curl.haxx.se/bug/view.cgi?id=1215
2013-06-17 17:28:35 -04:00
.host.foo.com TRUE / FALSE 1896263787 injected yes
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
cookies: same domain handling changed to match browser behavior Cokie with the same domain but different tailmatching property are now considered different and do not replace each other. If header contains following lines then two cookies will be set: Set-Cookie: foo=bar; domain=.foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 Set-Cookie: foo=baz; domain=foo.com; expires=Thu Mar 3 GMT 8:56:27 2033 This matches Chrome, Opera, Safari, and Firefox behavior. When sending stored tokens to foo.com Chrome, Opera, Firefox store send them in the stored order, while Safari pre-sort the cookies. Closes #1050
2016-10-03 00:34:59 -04:00
.www.host.foo.com TRUE / FALSE 1993463787 test6 six
www.host.foo.com FALSE / FALSE 1993463787 test6 six_more
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