9
\$\begingroup\$

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:

http links

\$\endgroup\$
  • 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\$ – SevenSidedDie Jun 13 '17 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\$ – doppelgreener Jun 13 '17 at 22:20
  • \$\begingroup\$ That's probably what they would end up doing, unless there really are very few. \$\endgroup\$ – SevenSidedDie Jun 14 '17 at 2:59

You must log in to answer this question.

Browse other questions tagged .