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

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Osmose [:osmose, :mkelly]]

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'

Comment 1

[Osmose [:osmose, :mkelly]]

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.

Comment 2

[Osmose [:osmose, :mkelly]]

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

Comment 3

[Stephen Donner [:stephend] Not actively reading bugmail]

(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.