Bug 1772821

Summary: wget is ignoring no_proxy environment variable [rhel-8.1.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: Oneata Mircea Teodor <toneata>
Component: wgetAssignee: Tomáš Hozza <thozza>
Status: CLOSED ERRATA QA Contact: Ondrej Mejzlik <omejzlik>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 8.0CC: fkrska, fperalta, mruprich, omejzlik, psklenar, qe-baseos-daemons, shawn, thozza
Target Milestone: rcKeywords: Patch, Reproducer, ZStream
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: wget-1.19.5-8.el8_1.1 Doc Type: If docs needed, set a value
Doc Text:
Cause: Previously, when wget was checking the domain name contained in requested URL against domains defined in no_proxy environment variable, it didn't correctly handle situation when domain defined in no_proxy environment variable was prefixed with dot ".", e.g. "no_proxy=.redhat.com" Consequence: As a result, wget would incorrectly apply proxy settings on all subdomains of the domain, prefixed with dot ".", defined in no_proxy variable. E.g. it would apply proxy settings on domain name www.redhat.com even when no_proxy environment variable contained ".redhat.com" value. Fix: wget has been fixed to not to apply proxy settings to all subdomains of the domain, prefixed with dot ".", defined in no_proxy variable. Result: As a result, it would not apply proxy settings on domain name www.redhat.com when no_proxy environment variable containes ".redhat.com" value.
Story Points: ---
Clone Of: 1763702 Environment:
Last Closed: 2019-12-17 10:48:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1763702    
Bug Blocks:    

Comment 6 errata-xmlrpc 2019-12-17 10:48:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:4272