When pages are being served over HTTP, seems like plugin might be forcing all assets on the page to load over HTTP, even if they are currently being served over HTTPS.
It looks like there may be special rules set up for certain 3rd party services that serve all assets over HTTPS (which is what we are doing as well). Might it be better to just update the logic to no longer re-write existing https protocol assets to http?
The latest version should handle these kinds of cases using URL Mapping or the URL Filtering which allows you to force particular patterns to HTTPS or HTTP.
When pages are being served over HTTP, seems like plugin might be forcing all assets on the page to load over HTTP, even if they are currently being served over HTTPS.
It looks like there may be special rules set up for certain 3rd party services that serve all assets over HTTPS (which is what we are doing as well). Might it be better to just update the logic to no longer re-write existing https protocol assets to http?
Quick example:
URL returned from oEmbed endpoint:
Note
https
protocol and ssl-specific subdomain.Plugin re-writes to:
which results in a 404.