01-31-2022, 07:01 AM
- I did start a process of helping to move the site from HTTP to HTTPS last year, and we got past one hurdle with the hosting company turning it on. Once we got that figured out though, I discovered it wasn't as simple as flipping the switch to make the change because there's tons of mixed content hard coded into pages across the entire site. I did make some of the fixes but the scope got beyond me and this is evidence of an area where I a.) don't know where the files are and b.) haven't even looked at how, or have the skills to fix this.
- If you do want to use Chrome, this is actually an easy fix to force the browser to accept mixed content on a site-to-site basis. This page here explains is pretty clearly. I did this, refreshed the page and it works fine
- https://experienceleague.adobe.com/docs/target/using/experiences/vec/troubleshoot-composer/mixed-content.html?lang=en
How Do I Enable Mixed Content in My Browser? | Adobe Target
For more information, see Mixed Content on the Mozilla Developer Network (MDN) website.. Enabling mixed content in Google Chrome. If you’re visiting a site via a secure connection, Chrome verifies that the content on the web page has been transmitted safely.
experienceleague.adobe.com
- https://experienceleague.adobe.com/docs/target/using/experiences/vec/troubleshoot-composer/mixed-content.html?lang=en
- 3. The below files are what Chrome dev inspector is saying are unsecure on the forum.
[img=0x0]https://mail.google.com/mail/u/0?ui=2&ik=6636272827&attid=0.2&permmsgid=msg-f:1723382588530238910&th=17eaaf55597025be&view=fimg&fur=ip&sz=s0-l75-ft&attbid=ANGjdJ-aO_Y9rTXn8UrvZ6tJptUcX3gDaA_5to5248tql5AORdO2ozuSbHCSUdW9vAjUS8o10hvmUvam-E-ko4XXbiZw7EMRmanQfxLeZhjbDAQ4IKJWZkqLTNW9FOQ&disp=emb[/img]
Jeff
KC1HDB
73, Steve - KC1SA