I think it would be better to persuade yum to interpret a 200 response to mean that the server could not complete the range request (in this case because it did not receive it), and has returned the complete content. It is common for content filtering proxies to strip range headers from requests, otherwise they could be effectively bypassed by a series of sufficiently small range requests.

Section 14.16 of RFC 2616 does not allow for proxies behaving in this way - if they are to function (and I think they are here to stay), the behaviour you are reporting is arguably the best available to them.

I'm sure there are enough people behind similar (possibly transparent) proxies to make accommodating this in yum worthwhile.

In reply to Re: Is wise to use HTTP::Proxy to enforce correct Content-Range responses? by flipper
in thread Is wise to use HTTP::Proxy to enforce correct Content-Range responses? by motobói

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.