Issuing multiple requests using HTTP/1.1 Pipelining
When using HTTP/1.1 Pipelining what does the standard say about issuing multiple requests without waiting for each request to complete? What do servers do in practice? I ask because I once tried writing a client which would issue a batch of GET requests for multiple files and remember getting errors. I wasn't sure if it was due to me incorrectly issuing the GET 's or needing to wait for each individual request to finish before issuing the next GET . Pipelining is just that -- having more than one request "in flight" on a single connection. On the open Internet, pipelining isn't very common,