768473 - Add CORS header for blog.cdn.mozilla.net

Status: RESOLVED INVALID

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

Description

[Craig Cook (:craigcook)]

The Mozilla blog (the main one, blog.mozilla.org) is using WP Super Cache to serve assets from a CDN, but that CDN (blog.cdn.mozilla.net) isn't sending correct CORS headers so some assets are being rejected by Firefox, most noticeably the web fonts.

Can we get a CORS header added to the CDN as soon as possible to fix this? 

I think "Access-Control-Allow-Origin: http://blog.mozilla.org" should do it? Not sure what the URL should be.

Comment 1

[Jake Maul [:jakem]]

I thought we fixed this yesterday right before the talk?

Comment 2

[Craig Cook (:craigcook)]

(In reply to Jake Maul [:jakem] from comment #1)
> I thought we fixed this yesterday right before the talk?

I thought so too but the fonts broke again today and I thought it was the same issue. Turns out it was and it wasn't.

Yesterday we pushed a change to Tabzilla that changed some font URLs to serve Open Sans from the Python site instead of the old PHP site. Those two sites, though their URLs are very similar, are hosted on different boxes. The PHP site sends a CORS header and the Python site does not. So by changing those font URLs it meant the Tabzilla fonts were being served from a non-CORS server so Firefox won't load them, and because the blog's style sheet uses the same name for that webfont (Open Sans Light) it broke fonts on every instance of One Mozilla because it embeds Tabzilla first (so Tabzilla's style sheet defines that font name before the blog's style sheet does).

So anyway, we've temporarily fixed Tabzilla to point back to the fonts on the PHP site and meanwhile we need to add a CORS header to mozilla.org, at least for some media assets served to some domains. That should be a separate bug.

Since it seems we're all set on the blog CDN we can call this invalid. Sorry.