Bug 47651 - Proxy setting not read correctly
Proxy setting not read correctly
Product: Red Hat Linux
Classification: Retired
Component: rhn_register (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2001-07-06 08:53 EDT by petr
Modified: 2015-01-07 18:47 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-06 08:53:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description petr 2001-07-06 08:53:41 EDT
Description of Problem:
Proxy setting defined by rhn_register --configure is not correctly used - first 7 characters of the hostname are truncated.

How Reproducible:

Steps to Reproduce:
1. rhn_register --configure
2. 1.  enableProxy        Yes, 2.  httpProxy          somename.somedomain:3128
3. tcpdump -s 300 host your_nameserver
4. rhn_register

Actual Results:
in tcpdump output can be seen that there is an "A" query for e.somedomain, i.e. for proxy name without first 7 characters.

Expected Results:
it shall be query for the right name.

Additional Information:
In rhnreg.py line 49
proxyHost = cfg.readEntry("httpProxy")[7:]
helps to change from 7 to 0:
proxyHost = cfg.readEntry("httpProxy")[0:]	
and then everything works fine.
Comment 1 Jay Turner 2001-07-06 10:29:42 EDT
This issue is resolved and the fix will be coming out in the next release of
Comment 2 Adrian Likins 2001-07-06 14:38:59 EDT
The short term fix is to use a proxy name in 
the format of "http://foo.bar.com:8192"

The comments in the config file indicate otherwise, but that will
be fixed in the new version as well.

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