A well-intentioned user has made a couple edits lately, where the only changes are updating "http:" links because they are "broken on HTTPS", by removing the leading "http:" in image (imgur) links. Note that the links aren't broken (the http: links still resolve). There are no other content changes in those edits.
Unfortunately, Stack Exchange has not implemented SSL site-wide yet. Until then, the image uploader will continue to generate "http:" links instead of "https:" links.
As of this posting, there are 4722 posts on Photo.SE containing "http://i.stack" (that is, http: links to the imgur hosting). It seems to me the way toward "https:" is not by editing every single post containing them; rather, a simple database script can update those when the sites go full HTTPS and when the image uploader creates the proper HTTPS links.
I rejected one such edit, and after seeing it, found another recent edit and rolled it back. But that got me wondering about the whole thing, and came here for calibration:
- Am I wrong to reject such edits?
- Am I wrong to rollback such revisions?
- https://photo.stackexchange.com/revisions/46683/7 (I rolled this one back)
For the interested, here are various meta SE posts about the transition to HTTPS/SSL:
- Better HTTPS support for Stack Exchange sites
- Untrusted connection when visiting per-site meta over SSL
[ssl]tag wiki has this to say:
Note that HTTPS is not officially supported by SE yet. While your page will load, the interesting bits will probably be broken. Do not expect HTTPS-related reports to be given high priority. (Expect friendly comments about how HTTPS is not officially supported yet.)
- Stackoverflow.com: the road to SSL - 3+ year old blog post by SO developer Nick Craver
Update March 2017
As Philip Kendall noted in comments (and reflected in his answer), Stack Exchange is going to be taking care of this on all SE sites soon: Roadmap to HTTPS: serving and uploading HTTPS-images only.