1336489 - Switch the bugzfeed app to SNI based SSL

Status: RESOLVED INVALID

(mozilla.org :: Heroku: Administration, task)

Description

[Ed Morley [:emorley]]

The bugzfeed Heroku app is one of the ones using the legacy SSL addon (see bug 1331583).

However the app appears broken and so presumably is unused, so could possibly be decommissioned instead, to save even more money.

ie HTTP 400s from:
https://bugzfeed.herokuapp.com/
https://bugzfeed.mozilla.org/

Mark, do you know what the status/plans are for this app? :-)

Comment 1

[Mark Côté [:mcote]]

It is still working; it's just that the service is only providing a WebSockets interface.  You can see it in use at https://people.mozilla.org/~mcote/bugzfeed_example/, which successfully connects to wss://bugzfeed.mozilla.org/.

I'll look into switching SSL solutions.

Comment 2

[Ed Morley [:emorley]]

Ah so could it perhaps return an HTTP 200 with a clearer message, or else a redirect to the docs etc? An HTTP 400 makes it look broken.

Re switching to SNI SSL, see bug 1331583 comment 12 for the rough process.

Many thanks! :-)

Comment 3

[Mark Côté [:mcote]]

Hi w0ts0n, you set up the SSL cert for bugzfeed on Heroku for me in bug 1292100.  Seeing as how I don't have access to the cert itself, are you able to upload it (or failing that, a new cert) to Heroku's SNI system?

Comment 4

[Mark Côté [:mcote]]

We're going to decommission bugzfeed instead.