fix: reject clients that do not send proper payload #18701
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Contribution License
All community contributions in this pull request are licensed to the project maintainers
under the terms of the Apache 2 license.
By creating this pull request I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 license.
Description
fix: reject clients that do not send a proper payload
Motivation and Context
nodes trying to connect to hosts that do not
trust them must reject with 403's
Currently, there are places where we keep the connection
active and mux server has to reject the connection with
a deadline later.
How to test this PR?
Start with a three-node setup and then expand with 2nd pool by adding 4th node but with the same three hosts from the previous pool with a new drive.
Please don't restart the first pool nodes, only start the second pool. Leads to random
errors showing up in the logs.
Types of changes
Checklist:
commit-id
orPR #
here)