Page MenuHomePhabricator

HTTPS redirects for config-master.wikimedia.org
Closed, ResolvedPublic

Description

Enabling this is trivial, the question is: is there any reason we *can't* enable this? Who's responsible for this service and might know of exceptions like mixed-content, or HTTPS-incapable tools which rely on it, etc? [note this a generic message being tacked into the description of several similar tickets]

Related Objects

StatusSubtypeAssignedTask
Resolved ema
DeclinedNone
ResolvedBBlack
ResolvedBBlack
ResolvedArielGlenn
ResolvedChmarkine
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
Resolved CCogdill_WMF
DeclinedBBlack
DuplicateBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack

Event Timeline

Re: rolematcher - the only real host I could trace it to in puppetization was fluorine. However, post-merge the update did not get applied there, so I think through some indirection I didn't look at closely enough, it's not really being actively deployed anywhere. I was under the impression udp2log was dead/dying anyways, so that's probably why!

Change 283190 had a related patch set uploaded (by BBlack):
config-master.wm.o HTTPS redirect T132459

https://gerrit.wikimedia.org/r/283190

Change 283190 merged by BBlack:
config-master.wm.o HTTPS redirect T132459

https://gerrit.wikimedia.org/r/283190

BBlack claimed this task.