Bug 1647517 - curl dropped HTTP/2 support
Summary: curl dropped HTTP/2 support
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: curl
Version: httpd24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
: 3.2
Assignee: Luboš Uhliarik
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
: 1691846 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-07 16:38 UTC by Joe Orton
Modified: 2020-04-15 08:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
The updated version of the cURL tool included in the httpd24 Software Collection does not support HTTP/2. Consequently, scripts reliant on HTTP/2 support in this version of cURL fail, or fall back to HTTP/1.1.
Clone Of:
Environment:
Last Closed: 2019-06-11 12:12:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1439 0 None None None 2019-06-11 12:12:59 UTC

Description Joe Orton 2018-11-07 16:38:41 UTC
Description of problem:
libcurl dropped HTTP/2 support in the rebase, not sure why.

Version-Release number of selected component (if applicable):
httpd24-curl-7.61.1-1.el7.x86_64

How reproducible:
  HTTP2 support:    disabled (--with-nghttp2)


Steps to Reproduce:
1.scl enable httpd24 'curl --version' | grep nghttp2

Actual results:
nada

Expected results:
.... nghttp2/1.34.0

Additional info:

Comment 9 Joe Orton 2019-03-25 13:02:44 UTC
*** Bug 1691846 has been marked as a duplicate of this bug. ***

Comment 18 errata-xmlrpc 2019-06-11 12:12:52 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://access.redhat.com/errata/RHEA-2019:1439


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