tests/cts/client-body-filter/data/test9

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