Please note that the workaround will stop working in may 2022 when chrome 102 is released, and that edge us sffected as well.
This is my final reply to 1st level support in my support issue (258485) on oct 19. @melih It saddens me to learn that 1st line seem to be unaware of the issue. It will not go away.
Note that according to the chrome/chromium time plan, the flag to disable the new behavior will be deprecated with Chrome 102
- May 2022: Chrome 102 rolls out to Stable. The deprecation trial ends. Chrome blocks all private network requests from public, non-secure contexts.
(This is from https://developer.chrome.com/blog/private-network-access-update/)
I also checked (in case any customer asks) – the flag is available in Microsoft Edge as well, and it is reached through edge://flags/ (search for insecure)