sourcecoast.com SSL problem

Alexandr,
Thanks for letting us know about that. We've fixed the problem for LinkedIn and will include it in the next release. In short, LinkedIn looks to be using a few different CDNs for their images. They only return the http:// version for the images from a specific CDN for some reason, while the rest come back as https. We've added some code to check for that CDN and automatically make it https if found.

Alex

No, schemeless links aren't the right way to go when loading from a social network. If you use a schemeless link, it can try to load the image over https if that's how you're viewing the current page.. but not every domain accepts https. If we used schemeless links for all images, then if the domain the social network returns doesn't support https, then you'll get an error and nothing will load. Other networks use a different URL to an image when it's loaded over http vs https (Facebook in particular), so you can't just add 's' (or use schemeless) to load the image.

So, for slidesharecdn.com, we had to make sure they support https. Then, we do a check to see if LinkedIn returned the http version of the image and that the https URL still worked with the same path. Now that it does, we change http to https.

it will reduce the number of requests.

This isn't true. If you use a schemeless link, it still uses the same amount of requests as if you were to force https for the link. It's just the browser automatically choosing http or https, but after that, it's requested and loaded the same way.

Thanks,
Alex