Add test scenario client-body-filter-https
[privoxy.git] / tests / cts / client-body-filter-https / data / test9
1 <testcase>
2 <info>
3 <keywords>
4 HTTPS
5 HTTP POST
6 client-body-filter
7 # This test currently doesn't work as Privoxy truncates the request.
8 # Sending no Content-Length header is an error but truncating the
9 # request still doesn't seem ideal. Probably Privoxy should reject
10 # the request instead of forwarding it.
11 skip
12 </keywords>
13 </info>
14
15 <reply>
16 <data>
17 HTTP/1.1 200 OK
18 Connection: close
19 Content-Type: text/html
20
21 Received your input.
22 </data>
23 </reply>
24
25 <proxy-reply>
26 <data>
27 HTTP/1.1 200 Connection established\r
28 \r
29 HTTP/1.1 200 OK\r
30 Connection: close\r
31 Content-Type: text/html\r
32 \r
33 Received your input.
34 </data>
35 </proxy-reply>
36
37 <client>
38 <server>
39 https
40 </server>
41 <name>
42 Attempt to apply client-body-filter{blafasel-to-bumfidel} to client request without Content-Length header
43 </name>
44 <features>
45 proxy
46 </features>
47 <command>
48 --limit-rate 1000 -d "blafasel%repeat[5000 x padding]%" -H "Content-Length:" --insecure https://%HOSTIP:%HTTPSPORT/%TESTNUMBER
49 </command>
50 </client>
51
52 <verify>
53 <protocol nonewline="yes">
54 POST /%TESTNUMBER HTTP/1.1\r
55 Host: %HOSTIP:%HTTPSPORT\r
56 User-Agent: curl/%VERSION\r
57 Accept: */*\r
58 Content-Type: application/x-www-form-urlencoded\r
59 \r
60 bumfidel%repeat[5000 x padding]%
61 </protocol>
62 </verify>
63 </testcase>