Issue: While using some versions of Chrome and Edge to establish a connection between Desktop Host and web applications configured to run on the HTTP protocol, the connection may not be established.
Solution: To prevent cross-site request forgery (CSRF) attacks, Chrome has introduced some restrictions on versions 94 and above. Thus, requests to access private networks from insecure public websites are now deprecated. Similar versions of Edge that use the Chromium engine are also affected. You can configure Chrome and Edge to access restricted private networks from insecure public networks by changing the block-insecure-private-network-requests preference. For additional information, consult documentation from Chrome and Edge on private network access (PNA).
To configure Chrome, perform the following steps after opening a new tab in Chrome:
- In the address bar, enter chrome://flags/#block-insecure-private-network-requests.
- From the drop-down next to the Block insecure private network request preference, select Disabled.
To configure Edge, perform the following steps after opening a new tab in Edge:
- In the address bar, enter edge://flags/#block-insecure-private-network-requests.
- From the drop-down next to the Block insecure private network request preference, select Disabled.
Alternately, contact your system administrator to have your web applications configured to use only the HTTPS protocol.