[SRE-4642] Add original-x-forwarded header handling#24
Merged
Conversation
Prefer setting $forwarded_ with $http_x_original_forwarded headers if they exist, otherwise fallback to $proxy_x_forwarded headers.
Sithembiso-Mashinini
approved these changes
Mar 28, 2025
This file contains hidden or 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
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.
Overview
Adds the ability to set
X-Forwarded-*headers using a priority-based approach.Going forward, the values of
X-Original-Forwarded-*headers will be used if they exist, otherwise we fall back to the previous default values.Examples
With
X-Original-Forwarded-*headersIncoming request:
Outgoing proxy request:
Without
X-Original-Forwarded-*headersIncoming request:
Outgoing proxy request: