Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My sites run off a subdomain (yyy.example.com), but I’m required to include CSS files from the main domain (example.com). We run a CMS that doesn’t let me do any server-side stuff during the preview stage, so I’m stuck sending a page over https that includes a CSS import to http. All my IE users get a mixed content warning because of this.
Is there any client side way for me to prevent this, other than maintaining separate security settings for the domain on every client machine?
Make use of protocol-relative URL’s in the CSS links.
Thus so
instead of
It will automatically pick the protocol of the parent request, which should work fine for HTTPS as well.