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.
Comment 2RHEL Program Management
2010-06-02 19:05:20 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
rpm 4.4.x didn't use curl but rpm's internal networking code. And rpm >= 4.6.x simply calls out to curl, so if "curl <something>" from command line works, it should work with rpm too. If it doesn't...
Rpm by default calls curl with the following opts:
--silent --show-error --fail --location
One of those (--fail looks likely) causes curl to give up where it doesn't when you call it from the command line. Notice the "curl: (52) Empty reply from server" error from curl, maybe the proxy is reporting something funny here when referring to an internal address.
Hi Panu,
I understand, but weird thing is: If I try to add these options to curl in command line, it will download that file. While rpm is failing to do that.
Even If I force curl to use http/1.0 while talking to proxy, it will download desired file.
Another thing I do not understand, is while it's ok for rpm to communicate with EPEL repo. But it gives up communication with download.devel.redhat.com.
A fair amount of head-scratching later... the bug was as silly as it seemed mysterious: it's an extra trailing \n in the command line which rpm passes down to exec(), with the \n ending up as a part of the url. Which apparently some servers dont mind, some servers do. Doh :)
*** Bug 612727 has been marked as a duplicate of this bug. ***
Comment 13Miroslav Vadkerti
2010-08-05 14:22:56 UTC
VERIFIED as fixed in rpm-4.8.0-12.el6
Comment 14releng-rhel@redhat.com
2010-11-10 21:32:16 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.