WebUI - Session is tied to IP address only, not port

[PaJaSoft]

A persistent browser session is somehow tied to the IP address only. It is possible to have more opened tabs with Node UI for different node instances together and do some actions but only when those nodes are reachable on different IP addresses. If for some reason you have more nodes manageable through one IP address but different ports it isn't possible....

Case A (working)
Tab1: http://192.168.111.12:4449/
Tab2: http://192.168.111.13:4449/

Case B (not working)
Tab1: http://192.168.111.12:4449/
Tab2: http://192.168.111.12:4450/

For Case B, Tab 1 and Tab 2 is first populated - so connection to both nodes is established (user in logged-in) but when you switch the tab, user is logged-out automatically and needs to do login again each time you switch tabs. If tabs point to different IP addresses, the sessions survive for hours...

Simple reproducer:
I)
Lets have two docker nodes where port mapping is exported to host network (192.168.111.1/24) like (nodes operates to two different public Internet lines, so perfect and supported Mysterium scenario):
node A) 4449->4449
node B) 4449->4450

II)
You can open a first tab in web browser and open page 192.168.111.1:4449, do login and be logged in
You can open second tab in web browser and open page 192.168.111.1:4450, do login and be logged in
Switch over to tab 1 and you can see you were logged-out and need to login again

Possible fix:
Destroying a web session not based on the fact that it is the same IP (as above), but based on IP:PORT pair would fix that behavior.