https://bz.apache.org/bugzilla/show_bug.cgi?id=65361
Bug ID: 65361
Summary: 101 Switching Protocols - custom headers are not set
Product: Apache httpd-2
Version: 2.4.38
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy_wstunnel
Assignee: bugs@httpd.apache.org
Reporter: steffen.pro...@mateso.de
Target Milestone: ---
We are using mod_proxy_wstunnel to reverse proxy WebSocket connections via
Apache to our backend. We also use the "Header" directive to always set the
Strict-Transport-Security header:
Header always set Strict-Transport-Security "max-age=31536000"
We now found that certain responses don't contain the custom header. Especially
304 Not Modified doesn't contain it, which is explained in the RFC:
https://datatracker.ietf.org/doc/html/rfc2616#section-10.3.5
101 Switching Protocols doesn't contain the header as well for which I couldn't
find a sound explanation.
Is this a bug or am I missing a good reason why responses with status code 101
shouldn't contain any further headers?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org
