Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 1 commit into from
Sep 11, 2024

Conversation

aaugustin
Copy link
Member

Fix #1419.

@aaugustin
Copy link
Member Author

Needs a changelog and perhaps tests.

@aaugustin
Copy link
Member Author

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

@aaugustin aaugustin changed the title Stop if process_request/response fails the handshake. Stop if process_request/response aborts the opening handshake. Sep 11, 2024
@aaugustin aaugustin force-pushed the stop-if-connection-is-not-open branch 4 times, most recently from 51fb596 to 1c82b64 Compare September 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 aaugustin merged commit 98f236f into main Sep 11, 2024
8 checks passed
@aaugustin aaugustin deleted the stop-if-connection-is-not-open branch September 11, 2024 20:03
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.

process_request returning response runs connection handler
1 participant