Comment 1 for bug 1794982

@Julian,

bug 948461 is what brought this in.

Some important information to be aware of in that regard.
a.) The issue occurred on S3 backed mirrors. S3 had (has?) a bug in their pipelining implementation. (bug 948461 comment 21)
b.) I believe (confirmation requested) that Canonical no longer runs mirrors in S3 but rather uses http proxy mirrors inside AWS.
c.) The user has no control on whether or not a proxy in their path is broken with respect to pipelining. Thus it was just seen as safer to disable it.
d.) other non-S3 users have seen such problems (bug 948461 comment 36).

The result of all above is that merely stating "this is fixed and is faster if the workaround is backed out" is not sufficient. At very least we need some evidence that it is no longer a problem with S3 backed mirrors. Ideally we have some way of recreating the broken state and showing that it is no longer necessary any more.

We have to do due diligence before SRU, other wise we risk regressing user in a way that is non-trivial to fix (since package updates are potentially broken). So, I'd really like to see demonstrated:
 1.) old apt without workaround recreating the problem
 2.) old apt with workaround works
 3.) new apt without workaround works