https://bz.apache.org/bugzilla/show_bug.cgi?id=61283
Bug ID: 61283
Summary: proxy_wstunnel sends a second 502 if the backend sends
a final HTTP response
Product: Apache httpd-2
Version: 2.4.26
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy_wstunnel
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
This initially looked similar to bug 60717, but it seems like that might be a
coincidence.
If the configured ws:// backend for a proxy_wstunnel request immediately
returns a final response code and closes the connection instead of upgrading,
proxy_wstunnel will send an extra "Bad Gateway" response body after the
response that has already been sent. Here's an example where the backend is
responding to a client that hasn't sent a supported Sec-WebSocket-Version:
HTTP/1.1 400 Bad Request
Date: Wed, 12 Jul 2017 16:54:20 GMT
Server: Apache/2.4.28-dev (Unix) OpenSSL/1.0.2g
Sec-WebSocket-Version: 13,8,7
Content-Length: 226
Connection: close
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
</p>
</body></html>
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Bad Gateway</title>
</head><body>
<h1>Bad Gateway</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
</p>
</body></html>
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
