openresty / openresty/lua-resty-websocket
check the HTTP response status code and headers for websocket client
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 523
- Forks
- 112
- Avg merge
- 1d 16m
- Merged PRs (30d)
- 2
Description
Hello!
Recently I'm working on developing some features based on this library. However, it seems that the websocket.client doest not check the status code, headers when handshaking. This may need to be strengthened. Is there any plan for this?
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 tracing the websocket.client handshake entry point and inspect how the HTTP response is processed. Determine which status code and headers must be validated during the handshake; done means invalid responses are checked and the behavior is covered by the project's available tests.
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
- 35/100