tests/data/test599

   1 <testcase>
   2 <info>
   3 <keywords>
   4 HTTP
   5 HTTP POST
   6 chunked Transfer-Encoding
   7 </keywords>
   8 </info>
   9 #
  10 # Server-side
  11 <reply>
  12 <data>
  13 HTTP/1.1 302 OK
  14 Date: Thu, 09 Nov 2010 14:49:00 GMT
  15 Server: test-server/fake
  16 Location: 5990001
  17 Content-Length: 6
  18 Connection: close
  19 Content-Type: text/html
  20
  21 -foo-
  22 </data>
  23 <data1>
  24 HTTP/1.1 200 OK
  25 Date: Thu, 09 Nov 2010 14:49:00 GMT
  26 Server: test-server/fake
  27 Transfer-Encoding: chunked
  28 Connection: close
  29 Content-Type: text/html
  30
  31 32
  32 this data is slightly larger than the first piece
  33
  34 0
  35
  36 </data1>
  37
  38 <datacheck>
  39 HTTP/1.1 302 OK
  40 Date: Thu, 09 Nov 2010 14:49:00 GMT
  41 Server: test-server/fake
  42 Location: 5990001
  43 Content-Length: 6
  44 Connection: close
  45 Content-Type: text/html
  46
  47 HTTP/1.1 200 OK
  48 Date: Thu, 09 Nov 2010 14:49:00 GMT
  49 Server: test-server/fake
  50 Transfer-Encoding: chunked
  51 Connection: close
  52 Content-Type: text/html
  53
  54 this data is slightly larger than the first piece
  55 </datacheck>
  56
  57 </reply>
  58
  59 # Client-side
  60 <client>
  61 <server>
  62 http
  63 </server>
  64 # tool is what to use instead of 'curl'
  65 <tool>
  66 lib599
  67 </tool>
  68
  69 # Bug 3510057 pointed out that when following a location to a larger chunked
  70 # encoded page, the first size would still be used in the progress callback
  71  <name>
  72 HTTP GET with progress callback and redirects changing content sizes
  73  </name>
  74  <command>
  75 http://%HOSTIP:%HTTPPORT/599 log/ip599
  76 </command>
  77 </client>
  78
  79 #
  80 # Verify data after the test has been "shot"
  81 <verify>
  82 <file name="log/ip599">
  83 CL: -1
  84 </file>
  85 </verify>
  86 </testcase>