You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a websocket server doesn't have any way to identify the source of incoming connections. The most simple use case is logging the address of incoming connections against a server. One could also process requests differently based on incoming address/network.
I see this used to exist, but was reverted in d1f7eeb without explanation.
The text was updated successfully, but these errors were encountered:
Currently, a websocket server doesn't have any way to identify the source of incoming connections. The most simple use case is logging the address of incoming connections against a server. One could also process requests differently based on incoming address/network.
I see this used to exist, but was reverted in d1f7eeb without explanation.
The text was updated successfully, but these errors were encountered: