Please enable HTTP/2 on the BMO vservers in dev/stage/prod, over a reasonable period of time for testing.
It's a single radio button that can often be enabled without any further configuration, but should still be staged carefully along whatever series of dev/stage/prod are appropriate. This enables HTTP/2 between useragents and the load balancer only. Requests to the backend will continue to work fine as HTTP/1. Ensure that BMO functions as expected when the useragent presents multiple cookies over HTTP/2. When they're converted from an HTTP/2 cookie bundle to an HTTP/1 cookie bundle, a couple of very old cookie-parsing libraries break (not Perl ones specifically, just in general).
I recommend initially enabling this on BMO-dev, and then we can spend a couple weeks testing.
Set http2!enabled to yes under protocol settings for bugzilla-dev.
http2 + unbundled assets loads more or less instantly for me, and they're cached, and I was able to login effectively, etc.
Testing on -dev went extremely well, based on Dylan's ongoing commentary on Friday. I propose advancing to BMO-stage next Tuesday. Dylan, is that enough time to let the weekend's changes settle?
Yeah, that probably works. We won't be touching any of the caching headers for this, so it should be low risk.
:fubar, are you around next Tuesday for this one-click radio button event on BMO-stage?
(In reply to Richard Soderberg [:atoll] from comment #7) > :fubar, are you around next Tuesday for this one-click radio button event on > BMO-stage? I will be.
http/2 enabled on stage.
I've been meaning to update here -- but http/2 can be flipped on for prod. That will be a non-event as far as I can tell.
Kendall, I'd like this to go out today or at worst tomorrow early US/Eastern *if* that's okay with you and Dylan.
I'll go flip it now.
And HTTP/2 enabled on production. So far, all of these have only been applied to the https VS; the http VS all redirect to https, so I'm not sure if we need to enable it on both or not. atoll?
HTTP/2 is mandatory TLS, so an HTTP-only VIP would not be able to enable it.