openresty / openresty/lua-resty-websocket
bad RSV1, RSV2, or RSV3 bits
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 523
- Forks
- 112
- Avg merge
- 1d 16m
- Merged PRs (30d)
- 2
Description
Hello,
I'm implementing a websocket server using lua-resty-websocket. When I send small frames everything is okay. But when the frame is getting bigger, approx 32kB I start receiving this message:
bad RSV1, RSV2, or RSV3 bits
I also can avoid this message by using a bigger Timeout:
local wb, err = server:new { max_payload_len = 65000, timeout = 1500}
but the drawback of this is that the messages are processed in a way slower manner: 1.5seconds is a huge time for a near real time application.
Do someone encountred this issue before ? Any idea of how to solve it please ?
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
Start by reproducing the failure with lua-resty-websocket using a payload around 32kB, comparing the default timeout with timeout=1500 and max_payload_len=65000. Trace the WebSocket frame parsing that reports “bad RSV1, RSV2, or RSV3 bits” and determine whether the timeout changes the framing behavior. Done means identifying the cause and documenting or testing a reliable fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100