ledgetech / ledgetech/lua-resty-http
Question: 100-continue response timeout?
Open
Nobody has claimed this yet.
bug
- Dominant language
- Lua
- Stars
- 2.1k
- Forks
- 630
- PR merge metrics
- No merged PRs in 30d
Description
If http header contain “Expect": 100-contiue, and the server not response 100 OK.
Then the lua-resty-http will block here:
local function _handle_continue(sock, body)
local status, version, reason, err = _receive_status(sock) --luacheck: no unused
///block here....
if not status then
return nil,nil,nil, err
end
How to do?
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 in the _handle_continue function and inspect the _receive_status call where the request blocks when no 100 response arrives. Determine the expected behavior for a missing or delayed 100-continue response and verify it with the relevant lua-resty-http or OpenResty test entry points; done means the client no longer blocks indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx
- Domain
- api, backend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100