Add test scenario client-body-filter-https
[privoxy.git] / tests / cts / client-body-filter-https / data / test16
1 <testcase>
2 <info>
3 <keywords>
4 HTTPS
5 HTTP POST
6 client-body-filter
7 </keywords>
8 </info>
9
10 <reply>
11 <data>
12 HTTP/1.1 200 OK
13 Content-Length: 21
14 Content-Type: text/html
15
16 Received your input.
17 </data>
18 <data1>
19 HTTP/1.1 200 OK
20 Connection: close
21 Content-Type: text/html
22 X-Connection: swsclose
23
24 Received your input.
25 </data1>
26 </reply>
27
28 <proxy-reply>
29 <data>
30 HTTP/1.1 200 Connection established\r
31 \r
32 HTTP/1.1 200 OK\r
33 Content-Length: 21\r
34 Content-Type: text/html\r
35 \r
36 Received your input.
37 </data>
38 <data1>
39 HTTP/1.1 200 OK\r
40 Connection: close\r
41 Content-Type: text/html\r
42 X-Connection: swsclose\r
43 \r
44 Received your input.
45 </data1>
46 </proxy-reply>
47
48 <client>
49 <server>
50 https
51 </server>
52 <name>
53 Attempt to apply client-body-filter{blafasel-to-bumfidel} to client request that does not completely arrive in time on a reused connection. (based on test 10)
54 </name>
55 <features>
56 proxy
57 </features>
58 # Sending the first request to appease the test framework.
59 # We mainly care about the second request where we overwrite the Content-Length
60 # header so curl sends less data than Privoxy expects.
61 <command>
62 -s --insecure https://%HOSTIP:%HTTPSPORT/first-request/%TESTNUMBER --next -s --write-out '%{stderr}%{response_code}\n' --limit-rate 5000 -d "blafasel%repeat[100 x padding]%" -H "Content-Length: 8000" --insecure https://%HOSTIP:%HTTPSPORT/second-request/%TESTNUMBER
63 </command>
64 </client>
65
66 <verify>
67 <stderr>
68 400
69 </stderr>
70 </verify>
71 </testcase>