wolfSSL: Use LIBWOLFSSL_VERSION_HEX to decide whether or not to use WOLFSSL_X509_V_OK
[privoxy.git] / tests / cts / client-body-filter / data / test10
1 <testcase>
2 <info>
3 <keywords>
4 HTTP
5 HTTP POST
6 client-body-filter
7 </keywords>
8 </info>
9
10 <reply>
11 <data>
12 HTTP/1.1 200 OK
13 Connection: close
14 Content-Type: text/html
15 X-Connection: swsclose
16
17 Received your input.
18 </data>
19 </reply>
20
21 <client>
22 <server>
23 http
24 </server>
25 <name>
26 Attempt to apply client-body-filter{blafasel-to-bumfidel} to client request that does not completely arrive in time. (XXX: Privoxy sends a "Connection failed" message instead of a timeout message which would be more appropriate)
27 </name>
28 <features>
29 proxy
30 </features>
31 # Sending the first request to appease the test framework.
32 # We mainly care about the second request where we overwrite the Content-Length
33 # header with an incorrect value so curl sends less data than Privoxy expects.
34 <command>
35 -s http://%HOSTIP:%HTTPPORT/first-request/%TESTNUMBER --next -s --write-out '%{stderr}%{response_code}\n' --limit-rate 5000 -d "blafasel%repeat[100 x padding]%" -H "Content-Length: 10000" http://%HOSTIP:%HTTPPORT/second-request/%TESTNUMBER
36 </command>
37 </client>
38
39 <verify>
40 <stderr>
41 400
42 </stderr>
43 </verify>
44 </testcase>