Protocol Relative URLs Not Working

Brad MarkleUpdated on July 18, 2023 1 Minute 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.

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.

Need More Help?

By continuing to visit any webpage within this website, each visitor agrees to the use of cookies and tracking technologies, and further agrees to abide by our Universal Terms of Service, Privacy Policy, Cookie Policy, and any other terms and policies posted on this website.