You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS.
/forum/viewtopic.php?f=11&t=13377&e=1&view=unread#unread:1 Mixed Content: The page at 'https://universalmediaserver.com/forum/viewtopic.php?f=11&t=13377&e=1&view=unread#unread' was loaded over HTTPS, but requested an insecure script 'http://www.universalmediaserver.com/assets/vendor/jquery/jquery.min.js'. This request has been blocked; the content must be served over HTTPS.
so I'm not sure why the browser is choosing to load over http instead of https in that case.
It may be a bug with Chrome/ium (I'm using the Brave browser) but we can maybe work around it by hardcoding the https instead of using a relative URI. Not ideal to have to do that but worth a try
The text was updated successfully, but these errors were encountered:
This seems inconsistent. Sometimes on the forum, certain requests break because they are trying to load them from http despite being on https. I have just noted it on https://universalmediaserver.com/forum/viewtopic.php?p=43161&sid=9b742d6706328c99d796ffea8d4ba94c#p43161
The console shows entries like this:
but the weird thing is in the code it shows:
so I'm not sure why the browser is choosing to load over http instead of https in that case.
It may be a bug with Chrome/ium (I'm using the Brave browser) but we can maybe work around it by hardcoding the https instead of using a relative URI. Not ideal to have to do that but worth a try
The text was updated successfully, but these errors were encountered: