I am using django-embed-video to embed videos from YouTube and Vimeo on my site. It works quite fine. But now I switched to https and videos suddenly stopped to work. Have you any idea why?
Output from pip freeze
Django==1.5
distribute==0.6.34
django-embed-video==0.5
wsgiref==0.1.2
in console log I have had:
[blocked] The page at 'https://localhost:8000/articles/my-test/' was loaded over HTTPS, but ran insecure content from 'http://www.youtube.com/embed/g9fHqTOYpm4?wmode=opaque': this content should also be loaded over HTTPS.
Upgrade django-embed-video.
Support for HTTPS sites has been added in version 0.7. You can read more about this problem in issue in Github repository.
Related
Chrome Mixed Content Message
My site was enabled nginx pagespeed module and all resources are loaded in https but webp url ( created by pagespeed ) is in http. I got a not-secure notice from Chrome brower. How to fix it?
Mixed Content: The page at 'https://interview.tw/c/QHkN' was loaded over HTTPS, but requested an insecure image 'http://assets.interview.tw/images/xmask.jpg.pagespeed.ic.yjlu3AxgW4.webp'. This content should also be served over HTTPS.
I found out that ModPagespeedFetchHttps enable fix this problem.
So put it on your pagespeed.conf file, clean the pagespeed cache (sudo touch /var/cache/mod_pagespeed/cache.flush) and restart Apache.
Good luck.
I'm trying to push a website I created off of my personal page and onto a GitHub page. It is successfully up at https://kalysren.github.io/, but my Tumblr embed isn't showing up. I've tried it in both Firefox and Chrome with the same results. If I check its existing location, it shows up perfectly in both Firefox and Chrome. Any thoughts?
Your site is https, but the tumblr content is http. You therefore have mixed content, and this is why it's not loading. You need to either, change your gh-pages site to http, or change the tumblr embed to https, assuming that's supported.
As explained by #dundonian, your current problem is mixed content.
As Github pages is requiring https for sites created after June 15, 2016, so you cannot downgrade to http and remove mixed content problem. Nevertheless, it's better to serve over https.
Trying to get joshwarmuth.tumblr.com served over https just by changing url protocol to https is not enough because tumblr is redirecting to the http version.
It seems that you can now change this behavior from your tumblr blog settings and force tumblr to serve over ssl.
This has only started happening as of this morning. I have a wordpress website served via https, and all of the images on the site served via http aren't appearing all of a sudden. This only appears to be happening on Chrome (47.0.2526.73 m) and Firefox (41.0.1) however it appears to work on IE, and mobile safari.
this is called Mixed Content (Mixed Protocol),When the webpage is loaded over SSL (HTTPS protocol), most browsers expect all of the assets to be loaded over the same protocol. Some browsers will display an error about loading “insecure content” while others will just block the insecure content outright.
for fix that in wordpress there are two solutions that you can see here
I have a site that is loading over HTTPS.
I have a HTML5 audio element on that site (currently a fallback for a Flash player), that is loading a Shoutcast URL. The Shoutcast URL is loading using a regular HTTP URL, because it doesn't seem to work using HTTPS.
However, Chrome is showing that the page includes elements that aren't secure, and when I check he console, I see this message:
Mixed Content: The page at 'https://mysite.com/' was loaded over HTTPS, but requested an insecure video 'http://shoutcasturl.com:8000/;'. This content should also be served over HTTPS.
Is there any way to get rid of the error in Chrome, so that the site shows up as fully secure, without any errors?
Shoutcast doesn't seem to work over HTTPS, though I don't think there's a certificate on that server for that FQDN anyway, but it doesn't seem like that adding a SSL certificate to the Shouutcast server will change anything.
Any ideas?
Thanks!
The only way to get rid of this warning is to load all external resources from secure locations. Since Shoutcast doesn't support SSL, your site will not be fully secure as long as you are loading assets directly from them.
See this question for some fairly complicated suggestions on getting around the issue.
I have my personal Google Chrome extension that adds an iframe to every page.
Now, it worked perfectly until a couple of days earlier.
Now it wont work on https pages!
The iframe source is HTTP.
The console is reporting:
[blocked] The page at https://example.com ran insecure content from http://mysite.com
Now, I know about mixed content issue, but it worked perfectly before. Why isnt it working now and how to fix it?
Anyone?
Thanks
Well, a new chrome update was released a couple of days ago. Check the patch notes from that release if they changed anything security related to make Chrome extensions require both HTTP or both HTTPS, not mixed.