wolfSSL: Use LIBWOLFSSL_VERSION_HEX to decide whether or not to use WOLFSSL_X509_V_OK
[privoxy.git] / tests / cts / chunked-transfer-encoding / data / test20
1 <testcase>
2 <info>
3 <keywords>
4 HTTP
5 HTTP GET
6 chunked transfer encoding
7 </keywords>
8 </info>
9
10 <reply>
11 <data>
12 HTTP/1.1 200 OK\r
13 Date: Thu, 22 Jul 2010 11:22:33 GMT\r
14 Connection: close\r
15 Content-Type: text/html\r
16 Transfer-Encoding: chunked\r
17 X-Control: swsclose\r
18 \r
19 100\r
20 %repeat[255 x A]%
21 \r
22 100\r
23 %repeat[255 x B]%
24 \r
25 100 blafasel %hex[%00]hex%\r
26 %repeat[255 x C]%
27 \r
28 0\r
29 \r
30 </data>
31 </reply>
32
33 <client>
34 <server>
35 http
36 </server>
37 <name>
38 Chunked transfer encoding - Multiple chunks, invalid binary zero in chunk extension. XXX: Privoxy could simply ignore this.
39 </name>
40 <features>
41 proxy
42 </features>
43 <command>
44 --raw http://%HOSTIP:%HTTPPORT/chunked-transfer-encoding/%TESTNUMBER
45 </command>
46 </client>
47
48 <verify>
49 <protocol>
50 GET /chunked-transfer-encoding/%TESTNUMBER HTTP/1.1\r
51 Host: %HOSTIP:%HTTPPORT\r
52 User-Agent: curl/%VERSION\r
53 Accept: */*\r
54 \r
55 </protocol>
56 # XXX: Why does curl not consider this an error?
57 <errorcode>
58 0
59 </errorcode>
60 </verify>
61 </testcase>