Add functionality to allow running behind a reverse proxy with correct IP logging #4
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.
What
This adds the necessary configuration for Fiber to run behind reverse proxy and log the correct IP address of the caller
Why
Whenever someone is running this behind a reverse proxy, only the reverse proxies IP is logged. This is not very helpful for analytics.
How
ctx.IP()
according to the documentation.Small performance overhead gets generated by utilizing
EnableIPValidation
but this is a good way to ensure not returning spoofed, invalid IPs