1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
<?xml version="1.0" encoding="US-ASCII"?>
<testcase>
<info>
<keywords>
HTTPS
HTTP POST
client-body-filter
</keywords>
</info>
<reply>
<data>
HTTP/1.1 200 OK
Content-Length: 21
Content-Type: text/html
Received your input.
</data>
<data1>
HTTP/1.1 200 OK
Connection: close
Content-Type: text/html
X-Connection: swsclose
Received your input.
</data1>
</reply>
<proxy-reply>
<data>
HTTP/1.1 200 Connection established%CR
%CR
HTTP/1.1 200 OK%CR
Content-Length: 21%CR
Content-Type: text/html%CR
%CR
Received your input.
</data>
<data1>
HTTP/1.1 200 OK%CR
Connection: close%CR
Content-Type: text/html%CR
X-Connection: swsclose%CR
%CR
Received your input.
</data1>
</proxy-reply>
<client>
<server>
https
</server>
<name>
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)
</name>
<features>
proxy
</features>
# Sending the first request to appease the test framework.
# We mainly care about the second request where we overwrite the Content-Length
# header so curl sends less data than Privoxy expects.
<command>
-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
</command>
</client>
<verify>
<stderr>
400
</stderr>
</verify>
</testcase>
|
