openresty / openresty/lua-resty-websocket
websocket ratelimiting
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 523
- Forks
- 112
- Avg merge
- 1d 16m
- Merged PRs (30d)
- 2
Description
Hi. how Can I implement ws ratelimiting by using this module? not only based on the connection but also inspect all request and message which is come in a websocket connection. as you know by using a tool like websocat, users can initiate a connections and send many messages in one connection but in loadbalancer side I only see one connection in log.
Thanks for your answer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or entry point. Start by reviewing the module’s WebSocket API and its integration with ngx_lua/OpenResty, then establish whether per-message rate limiting is supported. Done would require a documented, verifiable approach or a clear statement of the module’s limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100