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.

Description of problem:

Sourceforge bug id -> #1204 -> http://sourceforge.net/p/curl/bugs/1204/

###
See https://github.com/bagder/curl/pull/60

Often times proxy servers add their own headers (like HTTP/1.0 200 Connection established) to responses on their way back to the client. The size of these headers was not taken into account when calculating CURLINFO_HEADER_SIZE before the change from this pull request.

The problem can be reproduced quite easily using the test program from https://gist.github.com/mj/5102778. In our case the proxy server at proxy:8080 was the default Squid that ships with Debian stable.
###


Version-Release number of selected component in my case:

   # rpm -qa |grep curl
   curl-7.19.7-37.el6_5.3.x86_64
   libcurl-7.19.7-37.el6_5.3.x86_64
   [...]

   # curl --version
   curl 7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.15.3 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
   [...]

How reproducible:

Use curl to connect to URL through proxy server.

Thank you for reporting the bug!

upstream commit:
https://github.com/bagder/curl/commit/bc6037ed

Hi,

is there any plan when QA will be processed/finished? Our customer is facing this problem and would really like to have this problem fixed. ;)

Thanks and kind regards
Stefan

Hi Stefan,

this bug is approved to be fixed in the RHEL 6.7 update.

Please contact Product Support if you need an accelerated fix for the issue.

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