When running a site in https, the content from soundcloud is blocked in chrome because it is not loaded over https. Here is the message I get in the chrome console:
[blocked] The page at '[page_path]' was loaded over HTTPS, but ran insecure content from 'http://w.soundcloud.com/player/?url=http://api.soundcloud.com/tracks/581...': this content should also be loaded over HTTPS.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | check-server-for-https-2314445-1.patch | 912 bytes | gerard ketuma |
Comments
Comment #1
gerard ketuma commentedHere is a patch for the module to fix this issue. Checks for https and changes the request url in the tpl file to match the server settings.
Comment #2
gerard ketuma commentedComment #3
slybud commentedThank you fot this patch that looks pretty clean and safe.
I will able to push it in 1.2 release in september.
However what about removing the protocol form the soundcloud url, which would work in every case ?
Something like : src="//w.soundcloud.com/player/?url=http://api.soundcloud.com/..."
Comment #4
slybud commentedI think that removing the protocol is the best approach : the rendering of the tpl can be cached in one way or another and this could lead to the same bug when a site is accessed by both http and https protocol
So this will lead to a 1.2 release :)
Comment #6
slybud commentedFixed in the new 1.2 release