"HTTP/2 is largely based on Google's experimental SPDY protocol, which was first announced in November 2009 as an internal project to increase the speed of the web."
The easiest way to "increase the speed of the web" is to reduce or eliminate data collection, surveillance and advertising-related garbage from websites
With HTTP/1.1 I get speeds that are faster than HTTP/2; I don't make requests for ads, tracking or telemetry
What is the "mitigation" for Apache's HTTP/2 failure
"2. Implement Temporary Mitigation
If immediate patching is not possible due to operational constraints, temporarily disable HTTP/2 support to eliminate the attack vector.
Edit the configuration file (such as httpd.conf) to restrict active protocols to HTTP/1.1 by removing h2 and h2c references:"
# Restrict protocols to HTTP/1.1
Protocols http/1.1
One "security researcher" tried to suggest "HTTP/1.1 must die"
His reason was not "speed" it was "security" problems with CDNs
As above, the (bogus) "justification" given for HTTP/2 wasn't "security" it was "speed of the web"
CDNs cannot implement HTTP/1.1
Apache cannot implement HTTP/2
Without the data collection, surveillance and ads, HTTP/1.1 is faster than HTTP/2 according to own tests
HTTP/2 came from internet advertising companies and "CDNs", HTTP/1.1 came from academics
An advertising company
Later joined by CDNs
But www users were not consulted
"HTTP/2 is largely based on Google's experimental SPDY protocol, which was first announced in November 2009 as an internal project to increase the speed of the web."
https://blog.cloudflare.com/introducing-http2
"[I]ncrease the speed of the web" at what cost
The easiest way to "increase the speed of the web" is to reduce or eliminate data collection, surveillance and advertising-related garbage from websites
With HTTP/1.1 I get speeds that are faster than HTTP/2; I don't make requests for ads, tracking or telemetry
What is the "mitigation" for Apache's HTTP/2 failure
"2. Implement Temporary Mitigation
If immediate patching is not possible due to operational constraints, temporarily disable HTTP/2 support to eliminate the attack vector.
Edit the configuration file (such as httpd.conf) to restrict active protocols to HTTP/1.1 by removing h2 and h2c references:"
One "security researcher" tried to suggest "HTTP/1.1 must die"His reason was not "speed" it was "security" problems with CDNs
As above, the (bogus) "justification" given for HTTP/2 wasn't "security" it was "speed of the web"
CDNs cannot implement HTTP/1.1
Apache cannot implement HTTP/2
Without the data collection, surveillance and ads, HTTP/1.1 is faster than HTTP/2 according to own tests
HTTP/2 came from internet advertising companies and "CDNs", HTTP/1.1 came from academics
As a www user, that's what I care about