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.
Bug 1168137 - curl closes connection after HEAD request fails
Summary: curl closes connection after HEAD request fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: curl
Version: 6.6
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Stefan Kremen
URL:
Whiteboard:
Depends On:
Blocks: 1168503
TreeView+ depends on / blocked
 
Reported: 2014-11-26 09:13 UTC by Filip Krska
Modified: 2018-12-09 19:15 UTC (History)
3 users (show)

Fixed In Version: curl-7.19.7-42.el6
Doc Type: Bug Fix
Doc Text:
DO NOT DOCUMENT (already out via 6.6.z)
Clone Of:
: 1168503 (view as bug list)
Environment:
Last Closed: 2015-07-22 05:44:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
backport of upstream bug 1124 (759 bytes, patch)
2014-11-26 09:13 UTC, Filip Krska
kdudka: review+
Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1254 0 normal SHIPPED_LIVE Moderate: curl security, bug fix, and enhancement update 2015-07-20 17:50:03 UTC

Description Filip Krska 2014-11-26 09:13:04 UTC
Created attachment 961541 [details]
backport of upstream bug 1124

Description of problem:

backport of upstream fix http://sourceforge.net/p/curl/bugs/1124/

When curl fails on HEAD request (e.g. keepalive packet from httpd) it immediately closes connection with

* no chunk, no close, no size. Assume close to signal end

message. This can lead to infinite loops when e.g. NTLM authentication is required (curl -v -I -L -k -s --ntlm -u ACCOUNT:PASSWORD https://URL/nonexistent.html).

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

curl-7.19.7-40.el6_6.1.x86_64


How reproducible:

Always

Steps to Reproduce:

1. setup httpd server with KeepAlive On
2. curl -v --head http://server/nonexistent.html
3. observe output

Actual results:

...
Content-Type: text/html; charset=iso-8859-1
* no chunk, no close, no size. Assume close to signal end

< 
* Closing connection #0


Expected results:

...
Content-Type: text/html; charset=iso-8859-1

< 
* Connection #0 to host localhost left intact
* Closing connection #0


Additional info:

Backport patch attached.

Comment 1 Kamil Dudka 2014-11-26 09:54:56 UTC
Thanks for the bug report and patch!

upstream commit:
https://github.com/bagder/curl/commit/85ce195f

Comment 5 Kamil Dudka 2014-11-26 14:57:48 UTC
Comment on attachment 961541 [details]
backport of upstream bug 1124

Looks good to me.

Comment 11 errata-xmlrpc 2015-07-22 05:44:09 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://rhn.redhat.com/errata/RHSA-2015-1254.html


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