[release/8.0] Forwarded Headers Middleware: Ignore XForwardedHeaders from Unknown Proxy#61623
Merged
wtgodbe merged 2 commits intorelease/8.0from May 8, 2025
Merged
Conversation
added 2 commits
April 22, 2025 22:32
wtgodbe
approved these changes
May 8, 2025
1 task
This was referenced Jul 25, 2025
Open
This was referenced Feb 26, 2026
Bump the nuget-production-dependencies group with 22 updates
Mide69/Open-Telementry-project-demo#137
Closed
Closed
Open
Closed
Open
Bump the nuget-production-dependencies group with 23 updates
PraveenKumarDova/opentelemetry-demo#144
Open
This was referenced Mar 5, 2026
Open
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
2 participants
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.
Backport of #61530 to release/8.0
/cc @BrennanConroy @yannic-hamann-abb
Forwarded Headers Middleware: Ignore XForwardedHeaders from Unknown Proxy
Description
If the
ForwardedHeadersMiddlewaremiddleware is used without usingXForwardedForthen theKnownNetworksandKnownProxieschecks are skipped.Fixes #61449
Customer Impact
Expectations for
KnownNetworksandKnownProxiessettings are not always met. If you aren't careful with configuring your app (careful meaning aware of this issue), you can end up allowing traffic you didn't intend to allow.Regression?
Risk
Runs a check that was already there but runs it in more cases.
Verification
Packaging changes reviewed?