@John_Nadeau I used the MJPEG streams from my Reolink cameras in a format similar to the one mentioned in your post, but note that it’s a local HTTP address (not HTTPS). I ended up integrating the camera feeds to Blue Iris and I used that, but I also had a reverse proxy (Caddy2) running in front of it, so I wouldn’t have been impacted by the Mixed Content bug recently introduced in the Chromium project.
The same concept applies though. It seems like most people are either reverting to a version of their preferred Chromium browser from before the 111 update (until Chromium fixes the issue properly) or are installing SSL Certs or using a reverse proxy like Caddy with SSL to work around the issue.