Closed Bug 1311562 Opened 8 years ago Closed 6 years ago

codefirefox.com is broken -- it redirects to HTTPS version, and then serves cert for triagebot.mozilla.org

Categories

(Community Building :: Partnerships, task)

Product:
Community Building
Component:
Partnerships
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: dholbert, Unassigned)

Details

STR: 1. Visit any of these URLs: http://codefirefox.com (this redirects to https version) https://codefirefox.com ACTUAL RESULTS: "Your connection is not secure" error-page. "Advanced" button shows: > codefirefox.com uses an invalid security certificate. > The certificate is only valid for triagebot.mozilla.org If I hold my nose & accept the cert, I end up at the Triage Robot site, not at the Code Firefox site. Deeper links into the codefirefox.com site produce cert-error-and-then-404s. E.g. if I search Google for codefirefox.com, I get these suggestions and others: http://codefirefox.com/videos http://codefirefox.com/tagged/Firefox ...which give me 404 after I accept the invalid cert. Filing this under the Triagebot component since it seems Triagebot has stomped on codefirefox (or something).
mhoye / bbondy-if-you're-still-watching-bugmail: do either of you know what's up here? Looks like Code Firefox website source code is still around at https://github.com/bbondy/codefirefox , FWIW.
Flags: needinfo?(mhoye)
bbondy has walked away from this project, but graciously let us take ownership of the domain name last week. I haven't had time to stand up the replacement site yet - I'm going to start working on that shortly.
Flags: needinfo?(mhoye)
Leaving this bug open for the time being, 'til I do.
Is this bug obsolete / defunct / etc?
I think so, basically. There doesn't seem to be anything at this site now (attempts at loading the site just time out, for me). I suspect we never came up with a replacement site and don't really have anything to put there. Anyway: there's no cert error anymore at least, so the issue in comment 0 is no longer a problem. :)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.