We have few local sites with unsafe ports i.e. 100,101,102,103. Those were working fine on google chrome with explicitly-allowed-ports in the shortcut target. Suddenly they
This bug was already found in the Canary branch: https://bugs.chromium.org/p/chromium/issues/detail?id=916025
Temporary solution is to disable the "Enable Network Service" option in the chrome://flags settings