mirror/curl
2
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2024-12-27 06:59:43 +08:00
Code Issues Packages Projects Releases Wiki Activity
8dfa378e52
curl/tests/data/test517

136 lines
4.4 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-23 10:25:56 +08:00
<testcase>
tests: add keywords to the last 7 tests lacking them
2014-04-03 17:06:24 +08:00
<info>
<keywords>
getdate
unittest
</keywords>
</info>
added test case 517: 22 tests of the curl_getdate() function
2004-11-16 05:49:35 +08:00
#
# Server-side
<reply>
</reply>
# Client-side
<client>
<server>
none
</server>
# tool is what to use instead of 'curl'
<tool>
lib517
</tool>
<name>
curl_getdate() testing
</name>
<command>
nothing
</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-02-01 07:58:58 +08:00
<stdout>
added test case 517: 22 tests of the curl_getdate() function
2004-11-16 05:49:35 +08:00
0: Sun, 06 Nov 1994 08:49:37 GMT => 784111777
1: Sunday, 06-Nov-94 08:49:37 GMT => 784111777
2: Sun Nov 6 08:49:37 1994 => 784111777
3: 06 Nov 1994 08:49:37 GMT => 784111777
4: 06-Nov-94 08:49:37 GMT => 784111777
5: Nov 6 08:49:37 1994 => 784111777
6: 06 Nov 1994 08:49:37 => 784111777
7: 06-Nov-94 08:49:37 => 784111777
8: 1994 Nov 6 08:49:37 => 784111777
9: GMT 08:49:37 06-Nov-94 Sunday => 784111777
10: 94 6 Nov 08:49:37 => 784111777
11: 1994 Nov 6 => 784080000
12: 06-Nov-94 => 784080000
13: Sun Nov 6 94 => 784080000
14: 1994.Nov.6 => 784080000
15: Sun/Nov/6/94/GMT => 784080000
16: Sun, 06 Nov 1994 08:49:37 CET => 784108177
17: 06 Nov 1994 08:49:37 EST => 784129777
18: Sun, 12 Sep 2004 15:05:58 -0700 => 1095026758
19: Sat, 11 Sep 2004 21:32:11 +0200 => 1094931131
20: 20040912 15:05:58 -0700 => 1095026758
21: 20040911 +0200 => 1094853600
Stefan Krause's mail to curl-library at 03 Sep 2008 made me add these two new date strings to get tested too.
2008-09-05 16:15:21 +08:00
22: Thu, 01-Jan-1970 00:59:59 GMT => 3599
23: Thu, 01-Jan-1970 01:00:00 GMT => 3600
Added a range of new fun date strings to try. This set of dates come from a mail posted to the http-state mailing list, from Adam Barth, and is said to be the set of date formats the Chrome browser code is tested against: http://www.ietf.org/mail-archive/web/http-state/current/msg00129.html libcurl parses most of them identically, but not all of them.
2009-08-12 19:18:55 +08:00
24: Sat, 15-Apr-17 21:01:22 GMT => 1492290082
25: Thu, 19-Apr-2007 16:00:00 GMT => 1176998400
26: Wed, 25 Apr 2007 21:02:13 GMT => 1177534933
27: Thu, 19/Apr\2007 16:00:00 GMT => 1176998400
28: Fri, 1 Jan 2010 01:01:50 GMT => 1262307710
29: Wednesday, 1-Jan-2003 00:00:00 GMT => 1041379200
30: , 1-Jan-2003 00:00:00 GMT => 1041379200
31: 1-Jan-2003 00:00:00 GMT => 1041379200
32: 1-Jan-2003 00:00:00 GMT => 1041379200
33: Wed,18-Apr-07 22:50:12 GMT => 1176936612
34: WillyWonka , 18-Apr-07 22:50:12 GMT => -1
35: WillyWonka , 18-Apr-07 22:50:12 => -1
36: WillyWonka , 18-apr-07 22:50:12 => -1
37: Mon, 18-Apr-1977 22:50:13 GMT => 230251813
38: Mon, 18-Apr-77 22:50:13 GMT => 230251813
39: "Sat, 15-Apr-17\"21:01:22\"GMT" => 1492290082
40: Partyday, 18- April-07 22:50:12 => -1
41: Partyday, 18 - Apri-07 22:50:12 => -1
42: Wednes, 1-Januar-2003 00:00:00 GMT => -1
43: Sat, 15-Apr-17 21:01:22 => 1492290082
44: Sat, 15-Apr-17 21:01:22 GMT-2 => 1492290082
45: Sat, 15-Apr-17 21:01:22 GMT BLAH => 1492290082
46: Sat, 15-Apr-17 21:01:22 GMT-0400 => 1492290082
47: Sat, 15-Apr-17 21:01:22 GMT-0400 (EDT) => 1492290082
48: Sat, 15-Apr-17 21:01:22 DST => -1
49: Sat, 15-Apr-17 21:01:22 -0400 => 1492304482
50: Sat, 15-Apr-17 21:01:22 (hello there) => -1
51: Sat, 15-Apr-17 21:01:22 11:22:33 => -1
52: Sat, 15-Apr-17 ::00 21:01:22 => -1
53: Sat, 15-Apr-17 boink:z 21:01:22 => -1
54: Sat, 15-Apr-17 91:22:33 21:01:22 => -1
55: Thu Apr 18 22:50:12 2007 GMT => 1176936612
56: 22:50:12 Thu Apr 18 2007 GMT => 1176936612
57: Thu 22:50:12 Apr 18 2007 GMT => 1176936612
58: Thu Apr 22:50:12 18 2007 GMT => 1176936612
59: Thu Apr 18 22:50:12 2007 GMT => 1176936612
60: Thu Apr 18 2007 22:50:12 GMT => 1176936612
61: Thu Apr 18 2007 GMT 22:50:12 => 1176936612
62: Sat, 15-Apr-17 21:01:22 GMT => 1492290082
63: 15-Sat, Apr-17 21:01:22 GMT => 1492290082
64: 15-Sat, Apr 21:01:22 GMT 17 => 1492290082
65: 15-Sat, Apr 21:01:22 GMT 2017 => 1492290082
66: 15 Apr 21:01:22 2017 => 1492290082
67: 15 17 Apr 21:01:22 => 1492290082
68: Apr 15 17 21:01:22 => 1492290082
69: Apr 15 21:01:22 17 => 1492290082
70: 2017 April 15 21:01:22 => -1
71: 15 April 2017 21:01:22 => -1
72: 98 April 17 21:01:22 => -1
73: Thu, 012-Aug-2008 20:49:07 GMT => 1218574147
disable the tests that differ between 32 and 64 bit
2009-08-28 02:15:38 +08:00
74: Thu, 999999999999-Aug-2007 20:49:07 GMT => -1
75: Thu, 12-Aug-2007 20:61:99999999999 GMT => -1
76: IAintNoDateFool => -1
parsedate: allow time specified without seconds The date format in RFC822 allows that the seconds part of HH:MM:SS is left out, but this function didn't allow it. This change also includes a modified test case that makes sure that this now works. Reported by: Matt Ford Bug: http://curl.haxx.se/bug/view.cgi?id=3076529
2010-09-27 22:54:02 +08:00
77: Thu Apr 18 22:50 2007 GMT => 1176936600
parsedate: detect more invalid dates better
2011-06-22 05:18:05 +08:00
78: 20110623 12:34:56 => 1308832496
79: 20110632 12:34:56 => -1
80: 20110623 56:34:56 => -1
81: 20111323 12:34:56 => -1
82: 20110623 12:34:79 => -1
Added a leap second test to test517
2011-06-24 12:20:29 +08:00
83: Wed, 31 Dec 2008 23:59:60 GMT => 1230768000
parsedate: handle cut off numbers better ... and don't read outside of the given buffer! CVE-2016-8621 bug: https://curl.haxx.se/docs/adv_20161102G.html Reported-by: Luật Nguyễn
2016-10-04 22:59:38 +08:00
84: 20110623 12:3 => 1308830580
85: 20110623 1:3 => 1308790980
86: 20110623 1:30 => 1308792600
87: 20110623 12:12:3 => 1308831123
88: 20110623 01:12:3 => 1308791523
89: 20110623 01:99:30 => -1
added test case 517: 22 tests of the curl_getdate() function
2004-11-16 05:49:35 +08:00
</stdout>
skip the test of "2094 Nov 6" for now, since the 64bit time_t systems return different values for it...
2005-03-09 15:56:32 +08:00
Fix comment typos in test 517
2012-11-14 19:53:47 +08:00
# This test case previously tested an overflow case ("2094 Nov 6 =>
skip the test of "2094 Nov 6" for now, since the 64bit time_t systems return different values for it...
2005-03-09 15:56:32 +08:00
# 2147483647") for 32bit time_t, but since some systems have 64bit time_t and
# handles this (returning 3939840000), and some 64bit-time_t systems don't
Fix comment typos in test 517
2012-11-14 19:53:47 +08:00
# handle this and return -1 for this, it turned very tricky to write a fine
skip the test of "2094 Nov 6" for now, since the 64bit time_t systems return different values for it...
2005-03-09 15:56:32 +08:00
# test case and thus it is now removed until we have a way to write test cases
# for this kind of things.
added test case 517: 22 tests of the curl_getdate() function
2004-11-16 05:49:35 +08:00
</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-23 10:25:56 +08:00
</testcase>
Reference in New Issue Copy Permalink