Per Jessen wrote:
Roger Oberholtzer wrote:
On Wed, Nov 18, 2015 at 11:30 AM, Per Jessen <per@computer.org> wrote:
Big files are often broken into multiple downloads, one segment each. For instance, if an rpm is 16Mb, it could be downloaded as 16 x 1Mb segments from 16 different mirrors. It played merry hell with our squid cache until I figured out what was going on.
But the Cisco Ironport firewall gets the full file on it's own and then repackages it for the client as needed.
I'm surprised Ironport can work that out, it's fairly complex. You're certain it does that? Ah, maybe it does indeed fetch the whole file first, but that would be ridiculous. If a 16Mb file is split into 16 segments, that could potentially cause 16 full downloads :-)
IIRC, the Ironport does not deal correctly with some HTTP directives correctly set by zypper/curl when this is happening. So it breaks things. zypper/curl are not the only victims of the Cisco Ironport bug.
Aha, that's interesting. zypper is certainly not the only one to use the segmented download, but the only other one I can think of right now is youtube.
Anyway, yes, it sounds like the ZYPP_MULTICURL option is in fact the solution you need.
To test whether it works, if you can get to run tcpdump/wireshark, you should be able to see the http requests and the 206 responses. The 206 response is a clear indicator that segmenting is active. -- Per Jessen, Zürich (15.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org