HTTP HTTP PUT Expect # Server-side # 417 means the server didn't like the Expect header HTTP/1.1 417 BAD swsbounce Date: Tue, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Content-Length: 0 HTTP/1.1 200 OK Date: Tue, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Content-Length: 10 blablabla HTTP/1.1 417 BAD swsbounce Date: Tue, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Content-Length: 0 HTTP/1.1 200 OK Date: Tue, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Content-Length: 10 blablabla no-expect # Client-side http HTTP PUT with Expect: 100-continue and 417 response http://%HOSTIP:%HTTPPORT/we/want/%TESTNUMBER -T %LOGDIR/test%TESTNUMBER.txt --expect100-timeout 99 # 1053700 x 'x', large enough to invoke the 100-continue behaviour %repeat[1053700 x x]% # Verify data after the test has been "shot" PUT /we/want/%TESTNUMBER HTTP/1.1 Host: %HOSTIP:%HTTPPORT User-Agent: curl/%VERSION Accept: */* Content-Length: 1053701 Expect: 100-continue PUT /we/want/%TESTNUMBER HTTP/1.1 Host: %HOSTIP:%HTTPPORT User-Agent: curl/%VERSION Accept: */* Content-Length: 1053701 %repeat[1053700 x x]%