<testcase> <info> <keywords> HTTP HTTP POST </keywords> </info> # # Server-side <reply> <data> HTTP/1.1 302 OK Date: Thu, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Location: 5990001 Content-Length: 6 Connection: close Content-Type: text/html -foo- </data> <data1> HTTP/1.1 200 OK Date: Thu, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Transfer-Encoding: chunked Connection: close Content-Type: text/html 32 this data is slightly larger than the first piece 0 </data1> <datacheck> HTTP/1.1 302 OK Date: Thu, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Location: 5990001 Content-Length: 6 Connection: close Content-Type: text/html HTTP/1.1 200 OK Date: Thu, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Transfer-Encoding: chunked Connection: close Content-Type: text/html this data is slightly larger than the first piece </datacheck> </reply> # Client-side <client> <server> http </server> # tool is what to use instead of 'curl' <tool> lib599 </tool> # Bug 3510057 pointed out that when following a location to a larger chunked # encoded page, the first size would still be used in the progress callback <name> HTTP GET with progress callback and redirects changing content sizes </name> <command> http://%HOSTIP:%HTTPPORT/599 </command> </client> # # Verify data after the test has been "shot" <verify> </verify> </testcase>