[R4R] Add x-forward-for log message when handle message failed
#60
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
unclezoro
force-pushed
the
x-forward-for
branch
from
fd805ef
to
0e797c5
Compare
abelliumnt
approved these changes
Jan 11, 2021
yutianwu
approved these changes
Jan 11, 2021
Pythonberg1997
pushed a commit
to Pythonberg1997/bsc
that referenced
this pull request
Mar 29, 2023
improve code of bsc p2p protocol
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.
Description
For some infura service, bsc client may run on Cloud behind CDN/ALB, there is a requirement for these node to know the client IP to trouble shoot some issue.
Rationale
Just add the one more log message
Example
add an example CLI or API response...
Changes
Notable changes:
Preflight checks
make build)make test)Already reviewed by
...
Related issues
... reference related issue #'s here ...