diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2017-07-24 14:30:41 +0200 |
|---|---|---|
| committer | David Kalnischkies <david@kalnischkies.de> | 2017-07-26 19:07:56 +0200 |
| commit | d7518dba50e2285c41c7002a1d86f876401fd9ea (patch) | |
| tree | 1e172f084046a2fa4d73959fd341da1f8f7483eb /test/integration/test-http-pipeline-messup | |
| parent | 85f4a655cdc4d16c1b95de6fad7f3cd955265e46 (diff) | |
fail earlier if server answers with too much data
We tend to operate on rather large static files, which means we usually
get Content-Length information from the server. If we combine this
information with the filesize we are expecting (factoring in pipelining)
we can avoid reading a bunch of data we are ending up rejecting anyhow
by just closing the connection saving bandwidth and time both for the
server as well as the client.
Diffstat (limited to 'test/integration/test-http-pipeline-messup')
0 files changed, 0 insertions, 0 deletions