Add CloudFront IP ranges as trusted for real_ip #1906
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.
This change will allow nginx to recurse past the CloudFront IP
addresses and store the correct client IP address in
$remote_addr
.It is important that the correct client IP is available for rate
limiting on the publish endpoint and logging.
This list will need to be updated periodically.
cc @pietroalbini - This should probably be deployed before we enable CloudFront on production.