Closed Bug 984052 Opened 7 years ago Closed 4 years ago

[meta] Use a CDN for static assets on Webmaker

Categories

(Webmaker Graveyard :: DevOps, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: michiel, Assigned: johns)

Details

based on the webmaker-dev mailing list, let's set up some AWS cloudfront CDN hosting without the need for a $600 SSL cert to be used by everything IE9+,

Due to technical limitations raised in the email thread, we'll want to do UA string sniffing and send ie8 and below on to the non-CDN localtions (UA for v8 contains *MSIE 8*, for v7 contains *MSIE 7*, probably not necessary but why not, for v6 *MSIE 6*)
I was wondering about how to do this in terms of HTML output, what if we took advantage of conditional comments like so:

<!--[if lt IE 9]>
... load resources from webmaker.org since this is < IE9
<![endif]-->
<!--[if gte IE 9]><!-->        
... load resources from blah.cloudfront.net since this is >= IE9
<!--<![endif]-->

Actually, now that I think about it, do we even need to have the conditional comment for IE8? It'll load the default *.cloudfront.net SSL cert.

So the initial page load won't be from a CDN, but we don't want that to be from a CDN anyways.

We should pick a website we want to setup with a CDN first, because we'll need to do some code fixes before we can use a CDN with any of our apps.
Summary: set up AWS-cloudfront without a $600 SSL cert, and hook into it for CDN purposes for IE8+ → [meta] Use a CDN for static assets on Webmaker
Closing this out as we move to deprecate the Webmaker Component.

Issues can be re-filed at https://github.com/mozillafoundation/mofo-devops/issues/new if required.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.