Closed Bug 643832 Opened 15 years ago Closed 15 years ago

Add AddType video/webm to SUMO (Thursday, 24 March @4pm PDT)

Categories

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

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jsocol, Assigned: nmaul)

Details

(Whiteboard: [3/24 4:00pm])

We need to add a type to the apache config on sumo production for webm (it's serving as text/plain right now). This should happen soon-ish but not right now. Maybe Thursday during the downtime window? Cww might have some insight on the best moment.
Assignee: server-ops → nmaul
Is there a sumo push this thursday? if so (and if not even) we can push this out during the thursday window, will just cause apache to gracefully restart.
Whiteboard: [3/24 4:00pm]
Added this config to puppet, waiting for maintenance window to push live.
(In reply to comment #1) > Is there a sumo push this thursday? if so (and if not even) we can push this > out during the thursday window, will just cause apache to gracefully restart. There is not, but we can go ahead and do this during the downtime window. Hopefully the CDN will pick up the Content-Type change without our intervention?
Yes, the CDN should pick that up. Worst case, we can do a CDN cache flush to force it to see the change.
Summary: Add AddType video/webm to SUMO → Add AddType video/webm to SUMO (Thursday, 24 March @4pm PDT)
This has been pushed. Please let us know if you have any trouble with it.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
How long should it take for this to take effect? I just tried one video and didn't work yet.
Unfortunately there's no ETA on this. We have confirmed that the servers themselves are working properly, and that it's just a CDN caching issue. I've tried to issue a cache purge on that front, but it's not working. I have a ticket open with CDNetworks to get this resolved, but I don't know what their response time is like. As soon as I have more information, I'll update this bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This has been resolved. I needed to clear my cache before it became apparent, but after that it worked perfectly. Here are the test URLs I was using: Origin (worked since the change earlier today): http://support.mozilla.com/media/uploads/gallery/videos/2011-03-16-10-11-50-bdc786.webm CDN (works since 30m ago): http://sumo-cdn.mozilla.net/media/uploads/gallery/videos/2011-03-16-10-11-50-bdc786.webm
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.