Mixed Content warning when serving over HTTPS
See original GitHub issueJust curious, I’m seeing a Mixed Content warning in Chrome Dev Tools Console:
Mixed Content: The page at 'https://www.mywebsite.com/' was loaded over HTTPS,
but requested an insecure video 'http://res.cloudinary.com/mycloudname/video/upload/v1/mypublicId.webm'.
This content should also be served over HTTPS.
How does one force https
when using this component?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
How to Quickly Fix Mixed Content Warnings (HTTPS/SSL)
A mixed content warning appears in a user's browser when the site they're trying to visit is loading HTTPS and HTTP scripts or...
Read more >Mixed content - Web security - MDN Web Docs - Mozilla
Mixed passive/display content is content served over HTTP that is included in an HTTPS webpage, but that cannot alter other portions of the ......
Read more >How to Find and Fix Mixed Content Warnings on HTTPS Sites
According to Google, mixed content occurs when HTML on a website loads over a secure HTTPS connection (thanks to a recently installed SSL ......
Read more >How to Quickly Fix SSL Mixed Content Warnings on Your ...
SSL mixed content occurs when your site is loaded over a secure HTTPS connection, but other resources on your site (such as images,...
Read more >Mixed Content - The HTTPS-Only Standard
When an HTTPS website references insecure (HTTP) resources, this is called mixed content. Browsers prevent an HTTPS website from loading most insecure ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I added the
secure
prop and it works. Thanks!The problem for us is that we do SSR which does not have access to
window.location.protocol
. So when it is rehydrated in the client not only is it mixed content but the app HTML does not match what React renders causing issues. The solution is manually setting thesecure
option.