Comment by mrjin
3 years ago
I cannot have such BS any more. So I deployed something on my home server and exposed it on a port just above 10000. And I tried to access it with Chrome, and it was blocked coz it on an unusual port!! So obviously one of them had to go. So Chrome went away from my network.
Port 10080 is blocked on most browsers[0] per the WHATWG "bad ports" list[1]. That particular port was added to the list due to the Slipstream attack[2] that made the news a few years ago[3].
You don't have to switch to a browser that ignores standard security mitigations. Just pick a different port for your service.
[0] I just tested Chrome, Firefox, and Safari.
[1] https://news.ycombinator.com/item?id=24955891