This is generally not allowed by browsers: Mixed content - Web security | MDN
My usual recommendation is to put reverse proxy that has HTTPS enabled in front of legacy resources that can't be upgraded to use HTTPS.
This is generally not allowed by browsers: Mixed content - Web security | MDN
My usual recommendation is to put reverse proxy that has HTTPS enabled in front of legacy resources that can't be upgraded to use HTTPS.