: How to get rid of mixed content warning when using cookie-less domain for static content? When I serve all website content from same domain (https://example.com), tools like pingdom keeps yelling:
When I serve all website content from same domain (https://example.com), tools like pingdom keeps yelling:
Serve static content from a cookieless domain
When I serve static content from cookie-less domain (http://cdn.example.com), Chrome says:
Mixed Content: The page at 'https://example.com/' was loaded over
HTTPS, but requested an insecure image
'http://cdn.example.com/img/xyz.jpg'. This content should also be
served over HTTPS.
How can I satisfy both conditions at the same time?
More posts by @Karen161
1 Comments
Sorted by latest first Latest Oldest Best
When I serve static content from cookie-less domain (http://cdn.example.com)
Just as the message says... Your "cookie-less domain" also needs to be HTTPS. eg. cdn.example.com.
Once you switch to HTTPS then everything must switch to HTTPS. It's all or nothing. This is for a reason... If you have resources on a non-secure HTTP connection then it is possible that "information" could be leaked over this non-secure connection and intercepted, which kind of defeats the point of having HTTPS in the first place.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.