fix: use axum-client-ip
to get the real client IP
#240
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
This PR adds using of
axum-client-ip
to get a real client IP which is included in theX-Forwarded
by callingSecureClientIp
. The AWS ELB uses X-Forwarded-for and SecureClientIp sourced it for a real IP.Following changes are made:
axum-client-ip
is added to theCargo.toml
as a dependency. We already have it as a relative dependency in theCargo.lock
so it will not add additional dependency weight.ConnectInfo
replaced withSecureClientIp
.Resolves #225
How Has This Been Tested?
Successfully built and run with
analytics
feature enabled.Due Diligence