Debian Codegraph @

curl/tests/data/test517

raw
1 #
2 # Server-side
3 <reply>
4 </reply>
5
6 # Client-side
7 <client>
8 <server>
9 none
10 </server>
11 # tool is what to use instead of 'curl'
12 <tool>
13 lib517
14 </tool>
15
16 <name>
17 curl_getdate() testing
18 </name>
19 <command>
20 nothing
21 </command>
22 </client>
23
24 #
25 # Verify data after the test has been "shot"
26 <verify>
27 <stdout>
28 0: Sun, 06 Nov 1994 08:49:37 GMT => 784111777
29 1: Sunday, 06-Nov-94 08:49:37 GMT => 784111777
30 2: Sun Nov 6 08:49:37 1994 => 784111777
31 3: 06 Nov 1994 08:49:37 GMT => 784111777
32 4: 06-Nov-94 08:49:37 GMT => 784111777
33 5: Nov 6 08:49:37 1994 => 784111777
34 6: 06 Nov 1994 08:49:37 => 784111777
35 7: 06-Nov-94 08:49:37 => 784111777
36 8: 1994 Nov 6 08:49:37 => 784111777
37 9: GMT 08:49:37 06-Nov-94 Sunday => 784111777
38 10: 94 6 Nov 08:49:37 => 784111777
39 11: 1994 Nov 6 => 784080000
40 12: 06-Nov-94 => 784080000
41 13: Sun Nov 6 94 => 784080000
42 14: 1994.Nov.6 => 784080000
43 15: Sun/Nov/6/94/GMT => 784080000
44 16: Sun, 06 Nov 1994 08:49:37 CET => 784108177
45 17: 06 Nov 1994 08:49:37 EST => 784129777
46 18: Sun, 12 Sep 2004 15:05:58 -0700 => 1095026758
47 19: Sat, 11 Sep 2004 21:32:11 +0200 => 1094931131
48 20: 20040912 15:05:58 -0700 => 1095026758
49 21: 20040911 +0200 => 1094853600
50 </stdout>
51
52 # This test case previously testes an overflow case ("2094 Nov 6 =>
53 # 2147483647") for 32bit time_t, but since some systems have 64bit time_t and
54 # handles this (returning 3939840000), and some 64bit-time_t systems don't
55 # handle this and returns -1 for this, it turned very tricky to write a fine
56 # test case and thus it is now removed until we have a way to write test cases
57 # for this kind of things.
58
59 </verify>