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

HTTP/1 client connection unsolicited messages should be treated as invalid #5500

Conversation

vietj
Copy link
Member

@vietj vietj commented Mar 4, 2025

Motivation:

The current implementation of HTTP/1 client connection fails the connection when it receives unsolicited messages and does not release them. Such messages should be properly released to avoid leaking referenced counted messages.

Changes:

Update the HTTP/1 client connection to handle unsolicited messages as invalid, since invalid messages are released by the invalid message handler.

…valid.

Motivation:

The current implementation of HTTP/1 client connection fails the connection when it receives unsolicited messages and does not release them. Such messages should be properly released to avoid leaking referenced counted messages.

Changes:

Update the HTTP/1 client connection to handle unsolicited messages as invalid, since invalid messages are released by the invalid message handler.
@vietj vietj added this to the 4.5.14 milestone Mar 4, 2025
@vietj vietj added the bug label Mar 4, 2025
@vietj vietj self-assigned this Mar 4, 2025
@vietj vietj linked an issue Mar 4, 2025 that may be closed by this pull request
@vietj vietj merged commit 879aee4 into 4.x Mar 4, 2025
7 checks passed
@vietj vietj deleted the http1-client-connection-unsolited-messages-should-be-handled-as-invalid-4.x branch March 4, 2025 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory leak bug in Http1xClientConnectionClass
1 participant