Enable HTTP/2 on BMO dev/stage/prod

NEW
Unassigned

Status

()

bugzilla.mozilla.org
Infrastructure
6 months ago
4 months ago

People

(Reporter: atoll, Unassigned)

Tracking

Production

Details

(Reporter)

Description

6 months ago
Please enable HTTP/2 on the BMO vservers in dev/stage/prod, over a reasonable period of time for testing.
(Reporter)

Comment 1

6 months ago
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).
(Reporter)

Comment 2

6 months ago
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.
(Reporter)

Comment 4

6 months ago
http2 + unbundled assets loads more or less instantly for me, and they're cached, and I was able to login effectively, etc.
(Reporter)

Comment 5

6 months ago
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?
Flags: needinfo?(dylan)
Yeah, that probably works. We won't be touching any of the caching headers for this, so it should be low risk.
Flags: needinfo?(dylan)
(Reporter)

Comment 7

6 months ago
:fubar, are you around next Tuesday for this one-click radio button event on BMO-stage?
Flags: needinfo?(klibby)
(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.
Flags: needinfo?(klibby)
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.
Flags: needinfo?(klibby)
(Reporter)

Comment 11

4 months ago
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.
Flags: needinfo?(klibby)
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?
(Reporter)

Comment 14

4 months ago
HTTP/2 is mandatory TLS, so an HTTP-only VIP would not be able to enable it.
You need to log in before you can comment on or make changes to this bug.