Skip to content

Don't call again_or_timeout on the success path#44

Open
pacujo wants to merge 1 commit intoWithSecureOpenSource:masterfrom
pacujo:fix-timer-state-on-success
Open

Don't call again_or_timeout on the success path#44
pacujo wants to merge 1 commit intoWithSecureOpenSource:masterfrom
pacujo:fix-timer-state-on-success

Conversation

@pacujo
Copy link
Copy Markdown

@pacujo pacujo commented Apr 17, 2026

On the success path, errno may contain a stale EAGAIN, causing again_or_timeout to advance timer_state from EXPIRED to REPORTED. A subsequent http_op_get_response_content call checks timer_state first and returns ETIMEDOUT if it sees REPORTED -- even though the response headers were received successfully.

On the success path, errno may contain a stale EAGAIN, causing
again_or_timeout to advance timer_state from EXPIRED to REPORTED.
A subsequent http_op_get_response_content call checks timer_state
first and returns ETIMEDOUT if it sees REPORTED -- even though the
response headers were received successfully.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant