We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The server::onWSRequest::originIsAllowed() should be intelligent enough to reject abuse (in websocket connections)
server::onWSRequest::originIsAllowed()
The text was updated successfully, but these errors were encountered:
First we should define "what is abuse" :)
1.- Too many connections from the same IP 2.- Check a blacklist?
N.- ... Discussion open ...
But don't forget that to many abuse controls can be managed by the firewalls in front of our server so don't re-invent the wheel ;)
Sorry, something went wrong.
Agree. Let's check with Antonio about what he thinks.
Also: Too many connections from different IPs to the same App (same Public Key) - Possible Private key leak?
No branches or pull requests
The
server::onWSRequest::originIsAllowed()
should be intelligent enough to reject abuse (in websocket connections)The text was updated successfully, but these errors were encountered: