CSS not loading probably due to browser update

[nobbynobbs]

Teann,

A few days ago, grometsplaza.net stopped rendering correctly for me.  At first, I thought it was a server-side problem, like someone may have deleted or modified a .CSS file, but I just looked at the main page using the browser's "Inspect" tool and see that the browser (Vivaldi, which is a modification to Google Chrome) is blocking two .CSS files: default2.css and plaza2.css because they're being loaded using http instead of https.

The actual error is:

Mixed Content: The page at 'https://www.grometsplaza.net/main.html' was loaded over HTTPS, but requested an insecure stylesheet 'http://grometsplaza.net/default2.css?v=6155'. This request has been blocked; the content must be served over HTTPS.

And the same for http://grometsplaza.net/plaza2.css.  My guess is that a recent update to the browser increased the strictness of encrypted page loads.

If you could change those http:// requests to https://, that should fix the problem and also make the site a little more secure.

Thank you!

[teanndaorsa]

I suspect it's more likely that one of the changes made while migrating the site to the new server has flushed this out. However there aren't any obvious references to those files using http://, which means that wherever it's happening, it's probably a subtle side effect of one of the rewrite rules in place.

The page code in main.html I see is quite explicit:
<link href="/default2.css?v=6155" rel="stylesheet" type="text/css">
<link href="/plaza2.css" rel="stylesheet" type="text/css">

So the only way that loads using http:// is if the original page request was http:// too, which is odd, because if you try to load http://www.grometsplaza.net/main.html the server should redirect you to the https:// version before it ever gets to loading the CSS files. If it's reproducible for you, a screenshot of the Network tab with the main.html request selected might help narrow it down.

Is anyone else seeing this?

[nobbynobbs]

I suspect it's more likely that one of the changes made while migrating the site to the new server has flushed this out. However there aren't any obvious references to those files using http://, which means that wherever it's happening, it's probably a subtle side effect of one of the rewrite rules in place.

The page code in main.html I see is quite explicit:
<link href="/default2.css?v=6155" rel="stylesheet" type="text/css">
<link href="/plaza2.css" rel="stylesheet" type="text/css">

So the only way that loads using http:// is if the original page request was http:// too, which is odd, because if you try to load http://www.grometsplaza.net/main.html the server should redirect you to the https:// version before it ever gets to loading the CSS files. If it's reproducible for you, a screenshot of the Network tab with the main.html request selected might help narrow it down.

Is anyone else seeing this?

When I inspect main.html, select those link lines, and open the properties view, I see the href is fully-- and properly-- expanded to "https://www.grometsplaza.net/default2.css?v=6155" and "https://www.grometsplaza.net/plaza2.css".  The browser should be loading from those URLs, but the security engine is blocking the load with the mixed content error and displaying http: instead of https:.

VERY STRANGELY, I just discovered that if I open the site with https://grometsplaza.net/main.html (no "www."), it loads fine.

I'm a hardware guy, and my HTML effectively stopped with the release of HTML5, so further troubleshooting is out of my element.  As I have a workaround, I'll use it, but let me if you want me to test changes.