https breaking – insecure stylesheet
-
Hi,
I noticed that my site had a message about my site wanting to load unsafe scripts. When I clicked it my https breaks, shifting from green to red. Forgive terminology but inexperienced with this sort of thing.
I get the following message when I use chrome to inspect the pages. I contacted the theme developer but he says it’s not something at his end. He can only get it to go by deactivating autooptimise.
Mixed Content: The page at ‘https://hastingsarrow.com/?p=71&preview=true’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://fonts.googleapis.com/css?family=Noticia+Text|Open+Sans:800’. This content should also be served over HTTPS.
?p=71&preview=true:1 Mixed Content: The page at ‘https://hastingsarrow.com/?p=71&preview=true’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://fonts.googleapis.com/css?family=Montserrat:400,700|Oxygen|Raleway’. This content should also be served over HTTPS.
autoptimize_e6dfbf9….js:3 JQMIGRATE: Migrate is installed, version 1.4.1
?p=71&preview=true:1 Mixed Content: The page at ‘https://hastingsarrow.com/?p=71&preview=true’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://fonts.googleapis.com/css?family=Noticia+Text|Open+Sans:800’. This content should also be served over HTTPS.
?p=71&preview=true:1 Mixed Content: The page at ‘https://hastingsarrow.com/?p=71&preview=true’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://fonts.googleapis.com/css?family=Montserrat:400,700|Oxygen|Raleway’. This content should also be served over HTTPS.When I deactivate autooptimise, it resolves the warning issue although the https break in the dashboard that happened when I initially loaded the unsafe scripts, remains.
I have checked all the settings and every entry of the web address is https, not http. I did update a while a month ago to https but haven’t had a problem before. Only after updating to the pro level of the theme.
I tried searching through the forums but I could be staring the answer in the face and probably not realise it. Is this a case of excluding these fonts somewhere in autooptimise?
Thanks.
- The topic ‘https breaking – insecure stylesheet’ is closed to new replies.