in reply to Re: Is wise to use HTTP::Proxy to enforce correct Content-Range responses?
in thread Is wise to use HTTP::Proxy to enforce correct Content-Range responses?

Yeah, it would be nice if one could persuade yum to do that. But, as wrote at http://wiki.linux.duke.edu/YumFaq , question 5: 
Q. 5: I get an "Errno -1 Header is not complete." error from yum - what the heck is going on?
A. It's probably a proxy somewhere between you and the repository. You may not think that a proxy is in the way even though it really is.

(...)

The solutions to this problem are:

- Get your proxy software/firmware updated so that it properly implements HTTP 1.1
- Use an FTP repository, where byte ranges are more commonly supported by the proxy
- Create a local mirror with rsync and then point your yum.conf to that local mirror
- Don't use yum
  • Comment on Re^2: Is wise to use HTTP::Proxy to enforce correct Content-Range responses?

Replies are listed 'Best First'.
Re^3: Is wise to use HTTP::Proxy to enforce correct Content-Range responses?
by flipper (Beadle) on Apr 16, 2008 at 21:36 UTC
    I think this is similar to the fuss about ECN in the Linux kernel - in an ideal world, everyone would follow the spec; in the real world, the yum developers are making life difficult for people behind these proxies, over which they may well have no control. See also Postel's prescription, TCP window scaling and standards mode - in this case I think that these proxies are not going to go away, and it's churlish not to work with them.
[reply]

In Section Seekers of Perl Wisdom