Disable HTTP2 on input.mozilla.org (possibly temporarily)

RESOLVED FIXED

Status

Infrastructure & Operations
WebOps: Other
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: mkelly, Unassigned)

Tracking

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2682] )

(Reporter)

Description

2 years ago
We're seeing some very odd issues on input.mozilla.org. We're getting failed requests due to missing CORS headers, but the failure may actually be the preflighted OPTIONS request getting a 411 Length Required, which is odd. We're also having some issues replicating the problem, because it seems to work fine via HTTP/1.1 and we're having trouble getting builds of curl that do HTTP/2.0.

While we'
(Reporter)

Comment 1

2 years ago
Whoops, early submit.

While we're trying to sort these things out I'd like to disable HTTP2 on input.mozilla.org to see if it fixes the issue. If it doesn't, we can re-enable afterwards.

Updated

2 years ago
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2682]
(Reporter)

Comment 2

2 years ago
Via IRC, cyliang disabled HTTP2 on input.mozilla.org and it fixes our issues. We've decided to keep it disabled for the time being, but leave it on in staging.

Thanks for all the help! :D
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
(In reply to Michael Kelly [:mkelly,:Osmose] from comment #0)
> We're seeing some very odd issues on input.mozilla.org. We're getting failed
> requests due to missing CORS headers, but the failure may actually be the
> preflighted OPTIONS request getting a 411 Length Required, which is odd.
> We're also having some issues replicating the problem, because it seems to
> work fine via HTTP/1.1 and we're having trouble getting builds of curl that
> do HTTP/2.0.

Just for cross-reference, the issue filed is bug 1255031.
You need to log in before you can comment on or make changes to this bug.