https://bz.apache.org/bugzilla/show_bug.cgi?id=58971
Bug ID: 58971
Summary: Upgrade header added in 2.4.18 causes discount from
NodeJS
Product: Apache httpd-2
Version: 2.4.18
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Core
Assignee: [email protected]
Reporter: [email protected]
Httpd 2.4.18 added the Upgrade response header when a newer version of HTTP
protocol is available. This is valid and allowed by the spec.
Unfortunately NodeJS does not handle this correctly resulting in clients using
that not being able to connect to an Apache Httpd server running 2.4.18 and
HTTP/2.
This is an error on the NodeJS side. They have fixed the issue, though it has
not been released yet and they are not able to easily backport it to previous
versions. More details here:
https://github.com/nodejs/node/issues/4334.
So it could be some time before this fix is available to all the NodeJS
clients.
While I appreciate this is not a bug on the httpd side, it is something that
has broken with the latest release, it affects a very popular and common
technology, and could limit the uptake of httpd and HTTP/2, which I'm sure none
of us want.
Would there be any possibility of adding a DoNotSendUpgradeHeader, which could
default to False, but would enable those affected to set this to True? Or a
SendUpgradeHeader might be less confusing from a double negative point of view
:-)
More details:
Issue raised with mod_http2 where @icing identified the problem:
https://github.com/icing/mod_h2/issues/73
Thanks,
Barry
--
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]
