Bug 161409

Summary: Yum has problems thru old squid proxy
Product: [Fedora] Fedora Reporter: david avery <david.avery>
Component: yumAssignee: Jeremy Katz <katzj>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: katzj
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-21 19:28:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
log of yum transaction none

Description david avery 2005-06-23 04:00:14 UTC 
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:
1.
2.
3.
  
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 04:00:16 UTC 
Created attachment 115851 [details]
log of yum transaction
Comment 2 Seth Vidal 2005-06-23 04:25:59 UTC 
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 19:28:46 UTC 
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 :)