Question
After Chrome introduced the new New permission prompt for Local Network Access | Blog | Chrome for Developers permission model, some users had seen issues with iframes that load resources from the local network (for example, internal tools or services hosted on 192.168.x.x or .local domains).
In a plain HTML page, to fix that you can add:
<iframe … allow="local-network-access"></iframe>
In io.Connect Browser, you don’t directly control the raw <iframe> tag, but configure iframe behavior through the Home configuration.
Answer
To enable the local-network-access permission for iframes opened within io.Connect Browser, configure the iframe permissions policy like this:
iframePermissionsPolicy: {
flags: "local-network-access"
}
This has the same effect as setting allow="local-network-access" on a regular iframe: it tells the browser that the iframe is allowed to access local network resources (subject to the browser’s own Local Network Access prompts and policies).
Note: The behavior is ultimately controlled by the underlying browser - that will work on Chrome, but might not work on other browsers.