Timeline for Why do stack.imgur images break https? [duplicate]
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 20, 2017 at 10:30 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Jun 3, 2016 at 8:24 | history | closed |
hichris123 Ward - Trying Codidact Werner Nathan Tuggy Patrick Hofman discussion Users with the discussion badge or a synonym can single-handedly close discussion questions as duplicates and reopen them as needed. |
Duplicate of Make all i.sstatic.net links protocol-relative | |
| Jun 3, 2016 at 2:03 | review | Close votes | |||
| Jun 3, 2016 at 8:24 | |||||
| Jun 2, 2016 at 22:29 | comment | added | user102937 | This looks more like a bug than a feature request. | |
| Jun 2, 2016 at 20:16 | comment | added | Nathan Tuggy | Honestly, it's simpler than checking for an HTTPS page. All image requests can be made over TLS safely no matter what the containing page is delivered with. So just modify the uploader to set HTTPS, do a single bulk rewrite of past i.stack.imgur.com links to their HTTPS versions, and you're done. | |
| Jun 2, 2016 at 16:38 | comment | added | Laurel | Don't get me wrong (I even up voted) but I am only going off the fact that the other security things haven't been fixed. If the team wants to prove me wrong by fixing this (and/or the other issues) they should do so. | |
| Jun 2, 2016 at 16:27 | comment | added | E.P. | @Laurel I'm not personally that concerned, but this looks like low-hanging fruit to me. Or perhaps the dev team can explain why they can't / don't want to implement it. | |
| Jun 2, 2016 at 16:03 | comment | added | Laurel | I wouldn't be so hopeful about getting this fixed, sadly enough. I would suggest that you use some HTTPS everywhere extension if you are that concerned. | |
| Jun 2, 2016 at 15:25 | history | asked | E.P. | CC BY-SA 3.0 |