HTTP pipelining multi # Server-side # Silly division of the first request is solely to appease the server which expects n_data_items == n_requests HTTP/1.1 200 OK Server: test-server/fake Content-Length: 4 584 HTTP/1.1 200 OK Server: test-server/fake Content-Length: 0 HTTP/1.1 200 OK Server: test-server/fake Content-Length: 5 585 HTTP/1.1 200 OK Server: test-server/fake Content-Length: 4 586 # Client-side http lib530 HTTP GET using pipelining (nonzero length after zero length) http://%HOSTIP:%HTTPPORT/path/584 # Verify data after the test has been "shot" GET /path/5840001 HTTP/1.1 Host: %HOSTIP:%HTTPPORT Accept: */* GET /path/5840002 HTTP/1.1 Host: %HOSTIP:%HTTPPORT Accept: */* GET /path/5840003 HTTP/1.1 Host: %HOSTIP:%HTTPPORT Accept: */* GET /path/5840004 HTTP/1.1 Host: %HOSTIP:%HTTPPORT Accept: */* HTTP/1.1 200 OK Server: test-server/fake Content-Length: 4 584 HTTP/1.1 200 OK Server: test-server/fake Content-Length: 0 HTTP/1.1 200 OK Server: test-server/fake Content-Length: 5 585 HTTP/1.1 200 OK Server: test-server/fake Content-Length: 4 586