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.
Description of problem: Need backport of upstream fix for mod_proxy_wstunnel bug:
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
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.