One setting is provided to control the pipeline depth in cases
where the remote server is not RFC conforming or buggy (such as
Squid 2.0.2). Acquire::http::Pipeline-Depth can be a value from 0
to 5 indicating how many outstanding requests APT should send. A
value of zero MUST be specified if the remote host does not
properly linger on TCP connections - otherwise data corruption will
occur. Hosts which require this are in violation of RFC 2068.
I guess an alternative to trying to SRU this everywhere it affects images would be to ask Amazon to support RFC 2068?
One setting is provided to control the pipeline depth in cases :http:: Pipeline- Depth can be a value from 0
where the remote server is not RFC conforming or buggy (such as
Squid 2.0.2). Acquire:
to 5 indicating how many outstanding requests APT should send. A
value of zero MUST be specified if the remote host does not
properly linger on TCP connections - otherwise data corruption will
occur. Hosts which require this are in violation of RFC 2068.
I guess an alternative to trying to SRU this everywhere it affects images would be to ask Amazon to support RFC 2068?