Bug 1396197

Summary:	Backport: mod_proxy_wstunnel - AH02447: err/hup on backconn
Product:	Red Hat Enterprise Linux 7	Reporter:	Robert Bost <rbost>
Component:	httpd	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED ERRATA	QA Contact:	David Jež <djez>
Severity:	unspecified	Docs Contact:
Priority:	urgent
Version:	7.2	CC:	bnater, djez, dmasirka, isenfeld, jorton, jreznik, luhliari, mfrodl, rbost
Target Milestone:	rc	Keywords:	Patch, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	httpd-2.4.6-51.el7	Doc Type:	Bug Fix
Doc Text:	Previously, httpd running in a container returned the 500 HTTP status code (Internal Server Error) when a connection to a WebSocket server was closed. As a consequence, the httpd server failed to deliver the correct HTTP status and data to a client. With this update, httpd correctly handles all proxied requests to the WebSocket server, and the described problem no longer occurs.	Story Points:	---
Clone Of:
Clones:	1429606 1429947 (view as bug list)		Environment:
Last Closed:	2017-08-01 21:36:44 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:
Bug Depends On:
Bug Blocks:	1298243, 1429606, 1429947

Description Robert Bost 2016-11-17 17:34:29 UTC

Description of problem: Need backport of upstream fix for mod_proxy_wstunnel bug:

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


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


How reproducible: Always


Steps to Reproduce:
Requires httpd docker container and can use https://github.com/dpallot/simple-websocket-server.git in another container.

Customer unable to reproduce with plain httpd on RHEL. Docker is required.

Actual results: Websockets requests end with 500 status, even after data.


Expected results: No 500 status


Additional info:

Comment 15 errata-xmlrpc 2017-08-01 21:36:44 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/RHBA-2017:2175