wolfSSL: Use LIBWOLFSSL_VERSION_HEX to decide whether or not to use WOLFSSL_X509_V_OK
[privoxy.git] / tests / cts / client-body-tagger-https / data / test9
1 <testcase>
2 <info>
3 <keywords>
4 HTTPS
5 HTTP POST
6 client-body-tagger
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 </reply>
19
20 <proxy-reply>
21 <data>
22 HTTP/1.1 200 Connection established\r
23 \r
24 HTTP/1.1 200 OK\r
25 Content-Length: 21\r
26 Content-Type: text/html\r
27 \r
28 Received your input.
29 </data>
30 </proxyreply>
31
32 <client>
33 <server>
34 https
35 </server>
36 <name>
37 Two requests to the same URL on a reused connection. The second one is blocked based on a tag applied with client-body-tagger{blafasel}. (based on test 1)
38 </name>
39 <features>
40 proxy
41 </features>
42 <command>
43 -s --write-out '%{stderr}%{response_code}\n' --insecure https://%HOSTIP:%HTTPSPORT/%TESTNUMBER --next -d blafasel -s --write-out '%{stderr}%{response_code}\n' --insecure https://%HOSTIP:%HTTPSPORT/%TESTNUMBER
44 </command>
45 </client>
46
47 <verify>
48 <protocol>
49 GET /%TESTNUMBER HTTP/1.1\r
50 Host: %HOSTIP:%HTTPSPORT\r
51 User-Agent: curl/%VERSION\r
52 Accept: */*\r
53 \r
54 </protocol>
55 <stderr>
56 200
57 403
58 </stderr>
59
60 </verify>
61 </testcase>