Document IPNetwork and ForwardedHeadersOptions.KnownNetworks obsolescence for .NET 10 #47899
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 PR documents the breaking change introduced in .NET 10 Preview 7 where
Microsoft.AspNetCore.HttpOverrides.IPNetwork
andForwardedHeadersOptions.KnownNetworks
have been marked as obsolete in favor ofSystem.Net.IPNetwork
andForwardedHeadersOptions.KnownIPNetworks
.The change affects developers using forwarded headers middleware who will now receive compiler warning
ASPDEPR005
when using the obsolete APIs:Changes made:
docs/core/compatibility/aspnet-core/10.0/ipnetwork-knownnetworks-obsolete.md
The documentation follows the established template and includes comprehensive migration guidance, affected APIs, and code examples to help developers update their applications.
Fixes #47622.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Internal previews