tests/data/test599

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