6

Currently, the API returns resources like this:

"high_resolution_icon_url": "http://cdn.sstatic.net/stackoverflow/img/apple-touch-icon@2.png",
"favicon_url": "http://cdn.sstatic.net/stackoverflow/img/favicon.ico",
"icon_url": "http://cdn.sstatic.net/stackoverflow/img/apple-touch-icon.png"

When storing this in a table, then embedding the images in a page later, this gives mixed content warnings when using HTTPS. The CDN seems to be perfectly happy serving content over HTTPS, so can we return those links instead?

"high_resolution_icon_url": "https://cdn.sstatic.net/stackoverflow/img/apple-touch-icon@2.png",
"favicon_url": "https://cdn.sstatic.net/stackoverflow/img/favicon.ico",
"icon_url": "https://cdn.sstatic.net/stackoverflow/img/apple-touch-icon.png"
  • Hmm, I thought they were returned protocol-relative at some point, maybe I'm misremembering. – Tim Stone Dec 5 '15 at 2:44
  • @TimStone That'd be even better, but I stopped short of asking for that because I'm not sure how some mobile platforms would handle protocol-relative links. – Undo Dec 5 '15 at 2:45
  • 2
    I have not encountered any mobile platform in the last few years that had any problems with protocol-relative URIs. – Nathan Osman Dec 5 '15 at 19:10

You must log in to answer this question.

Browse other questions tagged .