I have created this "Snow Removal Tracker" storymap
On the section "Thank a Plow Driver" I embed the page
https://data.orangeville.ca/Apps/SnowThanks/index.html
It works in all browsers except Edge (of course) where it doesn't load the iframe and the devtools cite
CSP14312: Resource violated directive 'default-src https: data: blob:' in Content-Security-Policy: ms-appx-web:///assets/errorpages/dnserror.html?NetworkStatusSupported=1#https://data.orangeville.ca/Apps/SnowThanks/index.html. Resource will be blocked.
It does show the iframe page in next section of the storymap with no problem
Is there something I can add to the headers of my page to make it work?
I'm not sure how to remedy this, any help would be great.
Solved! Go to Solution.
Hi Evan,
Can you please provide the version of Edge that you're noticing that this is not working on?
I'm using Microsoft Edge 44.17763.831.0 and i can see the custom iframe on the Thank a Plow Driver section of the story come through:
I however observe that Edge console logs indicate the geoevent stream service connected behind the scenes to show the comments don't seem to be available for open consumption as a web socket. But that isn't preventing the content of the HTML in showing up.
Thanks,
Aravind
Hi Evan,
Can you please provide the version of Edge that you're noticing that this is not working on?
I'm using Microsoft Edge 44.17763.831.0 and i can see the custom iframe on the Thank a Plow Driver section of the story come through:
I however observe that Edge console logs indicate the geoevent stream service connected behind the scenes to show the comments don't seem to be available for open consumption as a web socket. But that isn't preventing the content of the HTML in showing up.
Thanks,
Aravind
Weird, it seems that when I'm on our town network it doesn't want to iframe that page, but only in the edge browser?! Otherwise it works fine, especially outside our network (I tested it while my laptop was tethered to my phone and on data)... so I'm going to leave it at that.
The other issues are just my stream service and our geoevent configuration that I'm still working out to expose publicly.
Thanks