Forum Discussion
Solved
Mixed mode content download warning
After the recent update to v124 in Stable, all of a sudden we had a bunch of internal sites start throwing mixed mode content download warnings which blocked file downloads. I was able to bypass this...
Thanks for everyone's patience!
We have just posted an update in the Stable Release Notes. Please see:
Microsoft Edge release notes for Stable Channel | Microsoft Learn
-Kelly
Folowed by:
Good day to you.
At the moment we do not have any documentation from Microsoft that explicitly states that this is an intended change from Microsoft to provide enhanced security. And as for the wildcards, * is not an accepted value for this policy.
You can refer to https://go.microsoft.com/fwlink/?linkid=2095322 for more information on formatting the URLs.
Please feel free to reach out to us in case you have any questions.
Good day to you.
At the moment we do not have any documentation from Microsoft that explicitly states that this is an intended change from Microsoft to provide enhanced security. And as for the wildcards, * is not an accepted value for this policy.
You can refer to https://go.microsoft.com/fwlink/?linkid=2095322 for more information on formatting the URLs.
Please feel free to reach out to us in case you have any questions.
- You can add wildcards as long as they are formatted properly like [*.]domain.com. This has saved us by allowing 90% of our current domain in the allow list while we deal with other individual domains that come up.
That is what we ended up doing. Just dissapointed in the communication. Micorosft and Google could have sent this out weeks in advance so companies can get in front of it. Places like mine use change controls to which we just cant apply comany wide GPO's on the fly. It is what it is just highly unlike Microsoft to not have a write-up or a pre-emptive "hey haeds up"
- Completely understandable. Thankfully we are agile enough to respond to things like this very quickly, but having zero communication from Google or Microsoft on this change is unacceptable. At the very least, a single line in the changelog would have saved us hours of troubleshooting and downtime.
