1<testcase> 2<info> 3<keywords> 4HTTP 5HTTP POST 6chunked Transfer-Encoding 7</keywords> 8</info> 9# 10# Server-side 11<reply> 12<data> 13HTTP/1.1 302 OK 14Date: Tue, 09 Nov 2010 14:49:00 GMT 15Server: test-server/fake 16Location: %TESTNUMBER0001 17Content-Length: 6 18Connection: close 19Content-Type: text/html 20 21-foo- 22</data> 23<data1> 24HTTP/1.1 200 OK 25Date: Tue, 09 Nov 2010 14:49:00 GMT 26Server: test-server/fake 27Transfer-Encoding: chunked 28Connection: close 29Content-Type: text/html 30 3132 32this data is slightly larger than the first piece 33 340 35 36</data1> 37 38<datacheck> 39HTTP/1.1 302 OK 40Date: Tue, 09 Nov 2010 14:49:00 GMT 41Server: test-server/fake 42Location: %TESTNUMBER0001 43Content-Length: 6 44Connection: close 45Content-Type: text/html 46 47HTTP/1.1 200 OK 48Date: Tue, 09 Nov 2010 14:49:00 GMT 49Server: test-server/fake 50Transfer-Encoding: chunked 51Connection: close 52Content-Type: text/html 53 54this data is slightly larger than the first piece 55</datacheck> 56 57</reply> 58 59# Client-side 60<client> 61<server> 62http 63</server> 64# tool is what to use instead of 'curl' 65<tool> 66lib%TESTNUMBER 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> 72HTTP GET with progress callback and redirects changing content sizes 73</name> 74<command> 75http://%HOSTIP:%HTTPPORT/%TESTNUMBER %LOGDIR/ip%TESTNUMBER 76</command> 77</client> 78 79# 80# Verify data after the test has been "shot" 81<verify> 82<file name="%LOGDIR/ip%TESTNUMBER"> 83CL -1 84</file> 85</verify> 86</testcase> 87