diff options
| author | Julian Andres Klode <julian.klode@canonical.com> | 2018-08-31 16:07:07 +0200 |
|---|---|---|
| committer | Julian Andres Klode <julian.klode@canonical.com> | 2018-09-28 13:13:26 +0200 |
| commit | 3de7454c796f245371c33076ae01529d6d36d715 (patch) | |
| tree | 63022f84a52894f738b9f3eb7aabe227cf9bd09c /test/integration/test-bug-605394-versioned-or-groups | |
| parent | d66bd6e5e9ae96676e805cce43937a0528cebe1b (diff) | |
http: Stop pipeline after close only if it was not filled before
It is perfectly valid behavior for a server to respond with
Connection: close eventually, even when pipelining. Turning
off pipelining due to that is wrong. For example, some Ubuntu
mirrors close the connection after 101 requests. If I have
more packages to install, only the first 101 would benefit
from pipelining.
This commit introduces a new check to only turn of pipelining
for future connections if the pipeline for this connection did
not have 3 successful fetches before, that should work quite well to
detect broken server/proxy combinations like in bug 832113.
(cherry picked from commit df696650b7a8c58bbd92e0e1619e956f21010a96)
LP: #1794957
Diffstat (limited to 'test/integration/test-bug-605394-versioned-or-groups')
0 files changed, 0 insertions, 0 deletions