Protocol Relative URLs Not Working Updated on July 18, 2023 by Brad Markle 0 Minutes, 45 Seconds to Read Problem: I am using Protocol Relative URLs / relative URLs when referencing css and javascript. When I access my page over https / ssl, the css and js is being called over http / no ssl. It is resulting in the following javascript error: [blocked] The page at ‘https://www.domain.com/page.php’ was loaded over HTTPS, but ran insecure content from ‘https://www.domain.com/style.css‘: this content should also be loaded over HTTPS. Solution: If you are using the base tag within your header, the protocol being used in your base tag will be used when calling scripts using Protocol Relative URLs / relative URLs. <head> <base href='http://www.domain.com/page.php' /> </head> If you need to use the base tag in your head, make sure to adjust it so that it uses https when using ssl, and http when not using ssl. Share this Article Related Articles How to Run and Read a Traceroute: Troubleshooting Website Connectivity What Are Meta Tags? Guide to SEO Meta Tags & Best Practices Meta Descriptions and SEO Install Let’s Encrypt Free SSL Certificate on Ubuntu with Certbot How to Set Up a 301 Permanent Redirect via .htaccess & cPanel BlaB! AX Maintenance Mode How to Log in to BlaB! AX 6 Ways to Improve Website Accessibility How to Create HTML Pages with the CherryTree Note-Taking Application Connecting with Google Analytics in Jetpack
