Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The *Frontier::Client* Perl module no longer ignores proxy settings for HTTPS requests
When using the *Frontier::Client* Perl module to send an XML-RPC request to an HTTPS server through a proxy service, the proxy setting was previously ignored. Consequently, the request was sent directly to the HTTPS server and not through the proxy server. With this update, the *Frontier::Client* Perl module has been corrected to pass the proxy setting to an underlying *LWP::UserAgent* object for both HTTP and HTTPS schemata, and *Frontier::Client* now respects proxy setting also for HTTPS requests.
Description of problem:
When creating a new Frontier client with
my $client = new Frontier::Client('url' => $url, 'proxy' => $proxy);
the proxy setting is used only for the HTTP protocol. In many corporate networks FTP/HTTP/HTTPS connections to the Internet are allowed only via proxies so the newly created Frontier client will fail to contact servers over HTTPS.
This is due to the new method in Frontier/Client.pm:
$self->{'ua'}->proxy('http', $self->{'proxy'})
if(defined $self->{'proxy'});
Version-Release number of selected component (if applicable):
perl-Frontier-RPC-Client-0.07b4p1-9.el6.noarch
Comment 2RHEL Program Management
2012-09-07 05:00:17 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 5RHEL Program Management
2013-04-19 06:15:57 UTC
Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Created attachment 1200473[details]
Fix
This filters supported protocols correctly and it limits the schemata to http and https because XML-RPC is defined on top of HTTP only.
How to test:
(1) Install package providing "perl(Frontier::Client)".
(2) Perform this command:
$ perl -Ilib -MFrontier::Client -e 'Frontier::Client->new(q{url} => q{https://localhost/}, q{proxy} => q{http://localhost:2000/})->call(q{method})'
(3) Check the network traffic or error output.
Before: A TCP connection to localhost:443 is performed, if there is no listening server, error "500 Can't connect to localhost:443 (connect: Connection refused)" is printed to error output.
After: A TCP connection to localhost:2000 is performed, if there is no listening proxt server, error "500 Can't connect to localhost:2000 (connect: Connection refused)" is printed.
Alternatively, you can set up an HTTP proxy and and HTTPS XML-RPC service and check the request is send only via the proxy and not directly.
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://rhn.redhat.com/errata/RHBA-2017-0605.html
Description of problem: When creating a new Frontier client with my $client = new Frontier::Client('url' => $url, 'proxy' => $proxy); the proxy setting is used only for the HTTP protocol. In many corporate networks FTP/HTTP/HTTPS connections to the Internet are allowed only via proxies so the newly created Frontier client will fail to contact servers over HTTPS. This is due to the new method in Frontier/Client.pm: $self->{'ua'}->proxy('http', $self->{'proxy'}) if(defined $self->{'proxy'}); Version-Release number of selected component (if applicable): perl-Frontier-RPC-Client-0.07b4p1-9.el6.noarch