QtWebEngine seem to perform network connections through a separate QtWebEngineProcess.exe process. This can cause firewall configuration problems for locked-down systems, since whitelisting the Qt application EXE isn't sufficient to enable networking . Networking instead need to enabled by whitelisting QtWebEngineProcess.exe. However, this will also enable networking for any other QtWebEngine application installed to the same folder, which can be problematic.

Request

Please make it possible to make the QtWebEngine network communication in-process, so that firewall whitelisting becomes safe & intuitive. It would be preferable if in-process networking could be enabled through either a project build flag or run-time API.

Steps to reproduce

1. Build WebEngine Qt Quick Minimal Example.
2. Configure Windows Defender Firewall to block all outbound connections by default (see screenshot).
3. Whitelist "minimal.exe" in Windows Defender Firewall.
4. Start "minimal.exe".
5. Observe that app isn't able to display the web page.