In Roadmap to HTTPS: serving and uploading HTTPS-images only, Step 3 said:

After this is enabled, old posts that have HTTP images, accessible via HTTPS, will be edited accordingly. This will be an actual markdown change, attributed to the Community user, posts won't be bumped.

Today, I revisted an old post I'd made, which had images from HTTP URLs that were part of StackExchange, and found that the images were no longer displayed but instead replaced by text URLs. I had to edit the post manually to add an s after http and that worked just fine.

This change should have been made automatically. That it was not, indicates some bug or incompleteness in the script which adjusted image URLs. That bug may affect other posts too.

  • Probably ".ico" extension wasn't included in the script, only common image extensions. It's not too late, they can add this and re-run the script. – Shadow The Dragon Wizard Oct 26 '17 at 7:20
  • Whatever set of extensions is used in deciding what to not load and display the error message for, should match the script used for adaptation. – WBT Oct 26 '17 at 12:45
  • Also, I wouldn't jump to blaming the .ico until surveying other examples, to find a pattern of .ico files never getting changed and all other extensions getting changed. – WBT Oct 26 '17 at 12:51

You must log in to answer this question.

Browse other questions tagged .