I found a spot on our site where links haven't been updated to HTTPS yet: our custom close reasons. The links in them still point to HTTP:// locations.
Here's an example:
\$\begingroup\$
\$\endgroup\$
3
asked Jun 13, 2017 at 21:36
-
1\$\begingroup\$ *groan*, that's annoying. They're a huge pain to update. Only Staff can update them in-place (that is, without them falling off all the posts). We'll have to bat-signal a CM. \$\endgroup\$– SevenSidedDieJun 13, 2017 at 22:18
-
\$\begingroup\$ @SevenSidedDie I figured they might set up a bot to sweep through the network-wide close reasons and update them. \$\endgroup\$– doppelgreenerJun 13, 2017 at 22:20
-
\$\begingroup\$ That's probably what they would end up doing, unless there really are very few. \$\endgroup\$– SevenSidedDieJun 14, 2017 at 2:59
Add a comment
|