Bug 1518737

Summary: HTTP/2 connections hang and timeout
Product: Red Hat Software Collections Reporter: David Mulford <dmulford>
Component: httpdAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Branislav Náter <bnater>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: httpd24CC: bgollahe, bnater, dmulford, jamills, jorton, kwalker, lkuprova, lzachar, tborcin
Target Milestone: alphaKeywords: Patch
Target Release: 3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the Apache HTTP Server from the httpd24 Software Collection was unable to handle situations when static content was repeatedly requested in a browser by refreshing the page. As a consequence, HTTP/2 connections timed out and httpd became unresponsive. This bug has been fixed, and HTTP/2 connections now work as expected in the described scenario.
Story Points: ---
Clone Of:
: 1569093 (view as bug list) Environment:
Last Closed: 2018-11-13 08:37:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1569093    

Description David Mulford 2017-11-29 14:23:28 UTC
Description of problem:
HTTP/2 connections hang and ultimately timeout. Details and patch available at the Apache bug below:

https://bz.apache.org/bugzilla/show_bug.cgi?id=61382

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

How reproducible:
Always

Steps to Reproduce:
1. Install httpd 2.4.27 with static content
2. Request static content in browser multiple times by repeatedly hitting refresh.

Actual results:
httpd will begin hanging, resulting in timeouts.

Expected results:
Requests are handled and return the expected content.

Comment 21 errata-xmlrpc 2018-11-13 08:37:01 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/RHSA-2018:3558