- Links in off-topic close reasons are not HTTPS.
- Links to other sites in migration close reasons are not HTTPS.
NB: This question is tagged "custom close reasons". Those include both the free-form close reasons users can provide, and the per site templated close reasons. I don't know if free-form close reasons also have this problem; I haven't tested it yet, and am reluctant to.
I did a spot-check of a few sites, and this is true for every site I checked.
I'm occasionally active on CodeReview.SE. That means closing questions every now and then (there really aren't that many off-topic ones, thankfully). While I was casting my close-vote, I wrote a comment to let the person know what they'd done wrong, so that they could try to fix it. To help, I copied a link from the off-topic close-vote reason, pasted it, and noticed that it started with
http://. Given Stack Exchange's recent migration to SSL, this surprised me, especially considering this bit:
Cleanup all existing user content that was http:// (https:// where possible, and converted to links if we can't embed it securely).
and it being marked with done. While I understand that close reasons are an... esoteric bit of user content, they are still user content, and should probably be retroactively modified.
At the very worst, a mass-email to the mods of every site would probably get it changed within a day; there are (if I'm remembering correctly) at most 5 site-specific close reasons. Apparently, that won't work. We need a dev to go in and change them directly.
The generic ones that all sites have are correctly migrated to HTTPS. However, none of the 3 close reasons on CR uses HTTPS links, and the Off-Topic > Migration options don't seem to, either.
I did a spot-check of a few other sites, and this is true for every site I checked.