Closed
Bug 882379
Opened 11 years ago
Closed 9 years ago
https://mzl.la/ is unreachable
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kohei, Unassigned)
References
()
Details
https://mzl.la/ is unreachable due to a timeout error.
http://mzl.la/ works well.
Comment 1•11 years ago
|
||
mzl.la services are routes through bitly. i personally don't have access to our bitly account, but will see if i can dig something up.
$ nslookup cname.bitly.com
...
Non-authoritative answer:
Name: cname.bitly.com
Address: 69.58.188.50
Name: cname.bitly.com
Address: 69.58.188.49
$ dig +short mzl.la
69.58.188.49
Comment 2•11 years ago
|
||
i tracked down credentials to our bitly enterprise account and reviewed the configuration. everything looks to be setup and functioning correctly. i do not see any way that https would work in this case -- bitly doesn't provide us a way to manage/support https.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 3•11 years ago
|
||
Oh, okay, other domains using the Bitly Enterprise service, like tcrn.ch or nyti.ms, are also unreachable when loading via SSL.
Status: RESOLVED → VERIFIED
Updated•11 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
This is quite bad. Every short link posted in social media networks, SUMO or elsewhere is vulnerable against MITM attacks.
There are open alternatives like https://yourls.org/
I vote for reopen.
Reporter | ||
Comment 5•9 years ago
|
||
One thing Mozilla could do here is to ask Bitly to adopt Let’s Encrypt this November to enable SSL for all the customers including Mozilla.
Assignee: server-ops-webops → nobody
Status: VERIFIED → REOPENED
Component: WebOps: Other → Social Media
Product: Infrastructure & Operations → Marketing
Resolution: INVALID → ---
Version: other → unspecified
Comment 6•9 years ago
|
||
Please open a new bug. The original request in this bug has nothing to do with Comment 4 and Comment 5.
Assignee: nobody → server-ops-webops
Status: REOPENED → RESOLVED
Closed: 11 years ago → 9 years ago
Component: Social Media → WebOps: Other
Product: Marketing → Infrastructure & Operations
Resolution: --- → FIXED
Version: unspecified → other
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•