Skip to content
New issue

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

Jump to bottom

Configured max_connections is not enforced on WebSocket listener #1735

Closed
ioolkos opened this issue Feb 20, 2021 · 1 comment
Closed

Configured max_connections is not enforced on WebSocket listener #1735

ioolkos opened this issue Feb 20, 2021 · 1 comment
Labels
bug websocket

Comments

@ioolkos
Copy link
Contributor

ioolkos commented Feb 20, 2021

If you configure a value for a maximal number of connections with something like listener.ws.my_ws.max_connections = 2, Verne doesn't seem to enforce the maximum number of WS connections. This only affects WebSockets.

This is not working as advertised, in other words: a bug :)
@ioolkos
Copy link
Contributor Author

ioolkos commented Feb 20, 2021

Or maybe it's not a bug but a feature :)
rabbitmq/rabbitmq-web-mqtt#28 (comment)

@ioolkos ioolkos closed this as completed Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug websocket
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ioolkos