3

My browser is reporting mixed HTTPS and HTTP content on the main site because the "Image of the week" in the header is HTTP:

<img src="http://i.stack.imgur.com/hJKvB.jpg" alt="Random Flower in Lawn">

Given that the rest of the imgur user-provided images were changed to HTTPS-only, it is obviously an oversight that whatever form the moderators have to edit the image of the week allows non-HTTPS URLs.

I'm tagging this as because the immediate problem is the image right now, and it will probably be a sufficient work-around for the mods to add the URL protocol to their mental checklist for updating the photo. Besides, since they know what the actual interface is, they're better placed than me to file a or .

  • I guess the issue is a lot of the photos submitted are a few years old, before they made the switch. It's not a big deal for us to try to remember to make sure it's https – MikeW Sep 5 '17 at 23:34
  • Interesting. Did the HTTPS-ification not include posts in meta? – scottbb Sep 6 '17 at 1:48
  • 2
    Related (or dupe?): “Parts of this page are insecure” warning from Firefox – Andrew T. Sep 6 '17 at 8:32
  • Possible duplicate of "Parts of this page are insecure" warning from Firefox – scottbb Sep 6 '17 at 12:42
  • lol, it feels weird to VtC a meta page as dupe. It's just so rare... =) – scottbb Sep 6 '17 at 12:43
  • @AndrewT This is not a dupe as it is a distinct occurrence. Dupe rules for Meta are a bit different since it also serves as something of a ticketing platform. – AJ Henderson Sep 6 '17 at 13:48
  • @scottbb see above comment. – AJ Henderson Sep 6 '17 at 13:48
  • @AJHenderson sure, I should have remembered. Un-VtC'd. – scottbb Sep 7 '17 at 13:10
2

Should be fixed now. Sorry. I missed that the image link wasn't https. The tool for setting that is literally just a block of HTML code that the mods are given access to directly modify and it gets injected. It apparently doesn't have any automatic https change over applied.

  • Just a suggestion, but since it's HTML you could leave a comment to remind you (plural) in the future. – Peter Taylor Sep 6 '17 at 14:08
  • @PeterTaylor it shouldn't be hard for me to remember. I just didn't realize they weren't automatically doing the conversion. I've dealt with many broken lock icons in my day. :) I'd rather not put a comment that has to be part of every page load. – AJ Henderson Sep 6 '17 at 14:23
  • 1
    If you're that worried about saving bytes, how about bare // URLs? – Peter Taylor Sep 6 '17 at 14:44
  • @PeterTaylor I like this plan! I'll admit I honestly didn't know (or had forgotten about) that shortcut. – AJ Henderson Sep 6 '17 at 14:50

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .