Do not send reject messages for bad services #2325
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reject message is deprecated, and has also been removed from the most recent protocol version entirely. Although the reject could be sent after a check of the negotiated pver, there's no value to sending a reject to a peer for bad advertised services. No message was ever rejected from being received by the remote peer.
dajohi
approved these changes
Jan 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The reject message is deprecated, and has also been removed from the most recent protocol version entirely.
Although the reject could be sent after a check of the negotiated pver, there's no value to sending a reject to a peer for bad advertised services. No message was ever rejected from being received by the remote peer.