In my setup, for reasons unrelated to this post, http://api.stackexchange.com web-site appears to be missing most of its resources, since even though the site itself is served over the http:// address scheme, a whole bunch of other rather mandatory Stack resources are hardlinked from cdn.sstatic.net with https:// (with certs issued by COMODO and/or Cloudflare).

The same is true of the i.stack.imgur.com images in the blog, e.g., http://blog.stackoverflow.com/2015/09/were-changing-our-name-back-to-stack-overflow/ has a couple of "enter image description here", and no images. No other Stack resources appear affected.

Perhaps it's possible to implement relative addressing, //, in place of the absolute ones, https://?

  • 2
    Yes. Yes. Yes. YES! You do not know how many times I wish this were likely this. Even if it's just for images using the uploading system, you do not know how much of an impact this would have! – Zizouz212 Feb 1 '16 at 2:58

You must log in to answer this question.

Browse other questions tagged .