Hi, Any news? I've tested with newest 184.108.40.2063. Bug is reproduced.
This problem is very actual for us, because our Application work as Service and accumulate data from other Servers on different users sides. Any user can change port forwarding from RO server to their IIS by mistake, so one or more CPUs on our server are going to High (100%) state. We detect this situation, stop connection to this user as temp solution, notify users about wrong port mapping, wait answer, check port forwarding, restore connection to user.
It is very uncomfortable. When this bug starts to be used specifically, this will be the end.