Skip to content

Stop if process_request/response aborts the opening handshake. - #1500

Merged
aaugustin merged 1 commit into
mainfrom
stop-if-connection-is-not-open
Sep 11, 2024
Merged

Stop if process_request/response aborts the opening handshake.#1500
aaugustin merged 1 commit into
mainfrom
stop-if-connection-is-not-open

Conversation

@aaugustin

Copy link
Copy Markdown
Member

Fix#1419.

@aaugustin

Copy link
Copy Markdown
MemberAuthor

Needs a changelog and perhaps tests.

@aaugustin

Copy link
Copy Markdown
MemberAuthor

Needs tests for sure because a new code path isn't covered.

@aaugustinaaugustin changed the title Stop if process_request/response fails the handshake.Stop if process_request/response aborts the opening handshake.Sep 11, 2024
@aaugustin
aaugustinforce-pushed the stop-if-connection-is-not-open branch 4 times, most recently from 51fb596 to 1c82b64CompareSeptember 11, 2024 05:33
When process_request() or process_response() returned a HTTP response
without calling accept() or reject() and with a status code other than
101, the connection handler used to start, which was incorrect.
Fix#1419.
Also move start_keepalive() outside of handshake() and bring it together
with starting the connection handler, which is more logical.
@aaugustin
aaugustinforce-pushed the stop-if-connection-is-not-open branch from 1c82b64 to 98f236fCompareSeptember 11, 2024 19:55
@aaugustin
aaugustin merged commit 98f236f into mainSep 11, 2024
@aaugustin
aaugustin deleted the stop-if-connection-is-not-open branch September 11, 2024 20:03
Sign up for freeto 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.

process_request returning response runs connection handler

1 participant

@aaugustin