Bug 161409 - Yum has problems thru old squid proxy
Yum has problems thru old squid proxy
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2005-06-23 00:00 EDT by david avery
Modified: 2014-01-21 17:52 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-21 15:28:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
log of yum transaction (3.66 KB, text/plain)
2005-06-23 00:00 EDT, david avery
no flags Details

  None (edit)
Description david avery 2005-06-23 00:00:14 EDT
Description of problem:
yum has problems when used thru a Squid 2.2STABLE5 proxy ( sidewinder 5.1 firewall)

Version-Release number of selected component (if applicable):
Yum 2.3.2 ( FC4 base)

How reproducible:
use yum thru a old squid proxy 

Steps to Reproduce:
Actual results:
yum fails after every http transaction and falls over to next mirror

finally falling off end of mirror list

Expected results:
yum should deal with proxy that can't do byte range ( only a guess)

Additional info:

see attachment
Comment 1 david avery 2005-06-23 00:00:16 EDT
Created attachment 115851 [details]
log of yum transaction
Comment 2 Seth Vidal 2005-06-23 00:25:59 EDT
yum requires the byte-range functionality of http 1.1.

If a proxy can't do it then we're more or less stuck.
Comment 3 Jeremy Katz 2005-09-21 15:28:46 EDT
At this point, byte ranges are required.  This requirement may disappear in the
future, but in general, it's going to be helpful for doing other things (think:
installing from ISOs that are stored on an HTTP server :)

Note You need to log in before you can comment on or make changes to this bug.