Closed
Bug 1251040
Opened 8 years ago
Closed 8 years ago
Please enable HTTP/2 on SUMO prod
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: stephend, Assigned: rwatson)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2604] )
We've had HTTP/2 enabled on SUMO staging (support.allizom.org) via bug 1250571 for nearly a full day, now - and have tested it via automation (https://webqa-ci.mozilla.com/view/SUMO/ is peachy-keen). Speaking with the folks cc:d here on IRC, we're ready to have it enabled in prod, when you get a chance; thanks!
Reporter | ||
Comment 1•8 years ago
|
||
:atoll/:w0ts0n - I think we're ready for this to be enabled on prod; would one of you mind doing the honors? Thanks! (Defaulting to Ryan for now, as he's been recently most-active in this area.)
Flags: needinfo?(rwatson)
Assignee | ||
Comment 2•8 years ago
|
||
Sure, ping me when you are online (as this is a big site) and we'll do it.
Assignee: server-ops-webops → rwatson
Flags: needinfo?(rwatson)
Assignee | ||
Comment 3•8 years ago
|
||
Leaving this bug un-done for a while. <stephend> w0ts0n: I'm going to hold off until we better understand what happened with Input (HTTP/2 might have been a factor - it was just disabled there so devs can sort out the cause of their POST problems) Will revisit later.
Reporter | ||
Comment 4•8 years ago
|
||
Also, by way of bug 1255031 which filed bug 1255489 (vendor-tracking bug against Brocade -- see https://bugzilla.mozilla.org/show_bug.cgi?id=1255031#c18), we'll revisit once that vendor bug is fixed, and we can (more) safely re-enable.
Can we verify that XHR/CORS is broken on support-stage in the same manner as it is on input-stage?
Reporter | ||
Comment 6•8 years ago
|
||
(In reply to Richard Soderberg [:atoll] from comment #5) > Can we verify that XHR/CORS is broken on support-stage in the same manner as > it is on input-stage? Wisely deferring to Mike/Michael.
Flags: needinfo?(mkelly)
Flags: needinfo?(mcooper)
Comment 7•8 years ago
|
||
Checking against Sumo API, CORS fails with HTTP 411 Length Required. In particular, I did this from an about:blank Firefox tab, in the console fetch('https://support.allizom.org/api/2/question/', {method: 'post', headers:{Authorization:'<auth>'}}).then(req => req.json()).then(data => console.log(data))
Flags: needinfo?(mcooper)
Reporter | ||
Updated•8 years ago
|
Flags: needinfo?(mkelly)
Comment 8•8 years ago
|
||
I'm guessing this is on hold for a while? If so, should we close this out for a while and re-open when it's ready to go?
Yup.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•