oaeproject/3akai-ux — pull request #3011 by nicolaasmatthijs (2013-06-25 10:52:15+00:00)
Title: Allow for oEmbed to be used on HTTPS

When using oEmbed on an https page, security conscious browsers such as Chrome won't load some of the http jsonp and swf content.

```
[blocked] The page at https://mydomain.org/mypage ran insecure content from http://flickr.com/services/oembed?format=json&url=http%3A//www.flickr.com/p…et-72157633424719011&jsoncallback=jQuery20006060085988137871_1372157077449.
```

In this PR, the providers we support have been made protocol agnostic and I've tested this on both http and https:

- blip.tv
- dailymotion
- deviantart
- flickr
- ifixit.com
- img.ly
- instagram
- pastebin.com
- pinterest
- scribd
- slideshare
- soundcloud
- speakerdeck
- ted.com
- twitgoo
- twitpic
- vimeo
- youtube

A PR has also been submitted to jQuery.oembed at https://github.com/starfishmod/jquery-oembed-all/pull/87