Bug 178816

Summary: yum not using the no_proxy environment variable
Product: [Fedora] Fedora Reporter: Hugo Cisneiros <hugo>
Component: python-urlgrabberAssignee: James Antill <james.antill>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: mstenner, taylor
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: 2008-04-30 00:27:52 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Hugo Cisneiros 2006-01-24 10:34:16 EST
Description of problem:

- As Linux console programs use the environment variables: http_proxy, ftp_proxy
and no_proxy, yum uses the first two, but ignores the no_proxy.

Version-Release number of selected component (if applicable):

yum-2.4.1-1.fc4

How reproducible:

Steps to Reproduce:
1. Configure proxy with the ENVVARS http_proxy, ftp_proxy and no_proxy
2. Configure a local repository that shouldn't use proxy (local, no_proxy var)
3. Try to yum update
  
Actual results:

yum tries to get the files throught proxy, even if the host is specified in the
no_proxy environment variable.

Expected results:

yum passes direct without proxy in hosts specified in no_proxy environment variable.

Additional info:

links/lynx, wget, perl, and many others programs read the no_proxy.
Comment 1 Christian Iseli 2007-01-22 05:51:50 EST
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.
Comment 2 Till Maas 2008-01-06 21:07:37 EST
This bug still exists in Fedora 7
Comment 3 Zachary Napora 2008-04-30 00:27:52 EDT
This might be two separate issues, but there clearly is something wrong with
yum(python) following the proxy syntax.

*** This bug has been marked as a duplicate of 191864 ***