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
73
74
75
76
77
78
79
80
81
82
83
84
85
|
<?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: 29%CR
Content-Type: text/html
Received your first request.
</data>
<data1>
HTTP/1.1 200 OK
Connection: close
Content-Type: text/html
X-Connection: swsclose
Received your second request.
</data1>
</reply>
<proxy-reply>
<data>
HTTP/1.1 200 Connection established%CR
%CR
HTTP/1.1 200 OK%CR
Content-Length: 29%CR
Content-Type: text/html%CR
%CR
Received your first request.
</data>
<data1>
HTTP/1.1 200 OK%CR
Connection: close%CR
Content-Type: text/html%CR
X-Connection: swsclose%CR
%CR
Received your second request.
</data1>
</proxy-reply>
<client>
<server>
https
</server>
<name>
Attempt to apply client-body-filter{blafasel-to-bumfidel} to client request on reused connection that is too large to buffer. (based on test12)
</name>
<features>
proxy
</features>
# We mainly care about the second request which is too large for Privoxy to buffer it.
<command>
--insecure https://%HOSTIP:%HTTPSPORT/first-request/%TESTNUMBER --next -d @log/post-data-%TESTNUMBER --insecure https://%HOSTIP:%HTTPSPORT/second-request/%TESTNUMBER
</command>
<file name="log/post-data-%TESTNUMBER">
blafasel%repeat[20000 x padding]%
</file>
</client>
<verify>
<protocol nonewline="yes">
GET /first-request/%TESTNUMBER HTTP/1.1%CR
Host: %HOSTIP:%HTTPSPORT%CR
User-Agent: curl/%VERSION%CR
Accept: */*%CR
%CR
POST /second-request/%TESTNUMBER HTTP/1.1%CR
Host: %HOSTIP:%HTTPSPORT%CR
User-Agent: curl/%VERSION%CR
Accept: */*%CR
Content-Length: 140008%CR
Content-Type: application/x-www-form-urlencoded%CR
%CR
blafasel%repeat[20000 x padding]%
</protocol>
</verify>
</testcase>
|
