tests/cts/client-body-filter-https/data/test10

   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 Connection: close
  14 Content-Type: text/html
  15 X-Connection: swsclose
  16
  17 Received your input.
  18 </data>
  19 </reply>
  20
  21 <proxy-reply>
  22 <data>
  23 HTTP/1.1 200 Connection established\r
  24 \r
  25 HTTP/1.1 200 OK\r
  26 Connection: close\r
  27 Content-Type: text/html\r
  28 X-Connection: swsclose\r
  29 \r
  30 Received your input.
  31 </data>
  32 </proxy-reply>
  33
  34 <client>
  35 <server>
  36 https
  37 </server>
  38 <name>
  39 Attempt to apply client-body-filter{blafasel-to-bumfidel} to client request that does not completely arrive in time. (XXX: Privoxy send a "Connection failed" message instead of a timeout message which would be more appropriate)
  40 </name>
  41 <features>
  42 proxy
  43 </features>
  44 # Sending the first request to appease the test framework.
  45 # We mainly care about the second request where we overwrite the Content-Length
  46 # header so curl sends less data than Privoxy expects.
  47 <command>
  48 -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
  49 </command>
  50 </client>
  51
  52 <verify>
  53 <stderr>
  54 400
  55 </stderr>
  56 </verify>
  57 </testcase>