-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Closed
Labels
✔️ Resolution: AnsweredResolved because the question asked by the original author has been answered.Resolved because the question asked by the original author has been answered.Status: Resolvedarea-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewares
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
A change in the recent 8.0.17 Release has made it so that if a request does not come from a known proxy or network in the forwarded header options the ForwardedHeadersMiddleware will ignore the forwarded headers. This is a breaking change because if you simply do not specify any known proxies or networks when creating the options the middleware will ignore all forwarded headers that worked in 8.0.16 and before.
Expected Behavior
If you don't specify any known networks or proxies the forwarded headers middleware should work as intended
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
No response
Anything else?
No response
Metadata
Metadata
Assignees
Labels
✔️ Resolution: AnsweredResolved because the question asked by the original author has been answered.Resolved because the question asked by the original author has been answered.Status: Resolvedarea-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewares