1246985 - Provision SSL certificates for *.browsercompat.org

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: BrowserCompat, defect)

Description

[John Whitlock [:jwhitlock]]

What problem would this feature solve?
======================================
Before switching to the production infrastructure, we'll need to protect HTTP requests with SSL, and have a plan for updating the certificates as they expire.

Who has this problem?
=====================
All visitors to MDN

How do you know that the users identified above have this problem?
==================================================================
In-browser JavaScript will request updated compatibility data. This data, and any assets linked in this data, need to use SSL.

How are the users identified above solving this problem now?
============================================================
On https://browsercompat.herokuapp.com, SSL is provided by the Heroku wildcard certificate.

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
https://letsencrypt.org may be a usable source for these certificates. A proposed URL scheme for BC services can be found at https://wiki.mozilla.org/MDN/Development/CompatibilityTables/Infrastructure#Production_Services

Is there anything else we should know?
======================================
SHA-256 certs should be used. API services can be configured with Modern compatibility settings: https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility

Comment 1

[John Whitlock [:jwhitlock]]

The BrowserCompat project is canceled.  See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.