|
|
|
|
|
by AgentME
2247 days ago
|
|
>Since Chrome v80 they forced <video> <img> content to switch to HTTPS, if the page itself is served https. Is it really a good idea? So for Intranet URLs with customize TLDs, you have exactly three choices If the intranet isn't set up to be able to serve over HTTPS, then wouldn't the intranet page be served over HTTP too and not make this an issue? Is it really common to have intranet sites where you have some of the endpoints covered by HTTPS and some not, and further, the HTTPS intranet page embedding content from intranet HTTP sites? |
|
The page itself is served in both HTTP and HTTPS, can be visited in and outside the LAN.
The <img> and <video> content fail in HTTPS without explanation in Chrome v81+