RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/dotnet/core/commit/c6c9df5f56a243bb1a68049619e54c0d8164128e below:

Update asp.net breaking change (#9934) · dotnet/core@c6c9df5 · GitHub

File tree Expand file treeCollapse file tree 2 files changed

+16

-0

lines changed

Filter options

Expand file treeCollapse file tree 2 files changed

+16

-0

lines changed Original file line number Diff line number Diff line change


 @@ -2,6 +2,14 @@

2 2 3 3


 You may encounter the following known issues, which may include workarounds, mitigations, or expected resolution timeframes.

4 4 5

+
 ## ASP.NET

6 + 7

+
 ### [8.0.17] Breaking Change: UseForwardedHeaders middleware now always checks ForwardedHeadersOptions.KnownNetworks and ForwardedHeadersOptions.KnownProxies

8 + 9

+
 `UseForwardedHeaders` middleware now always checks `ForwardedHeadersOptions.KnownNetworks` and `ForwardedHeadersOptions.KnownProxies`. Because both `KnownNetworks` and `KnownProxies` default to Loopback this means deployed applications may fail to apply `X-Forwarded-*` headers resulting in properties like scheme and host not being updated which can have side-effects e.g. `UseHttpsRedirection()` might always see http and always redirecting the request.

10 + 11

+
 The recommended fix is to set the `KnownNetworks` and `KnownProxies` values to the appropriate values. See https://learn.microsoft.com/aspnet/core/host-and-deploy/proxy-load-balancer for more details on using proxies and `UseForwardedHeaders()`. Alternatively, if you are fine accepting `X-Forwarded-*` headers from any source, which introduces security vulnerabilities, you can clear the `KnownNetworks` and `KnownProxies` properties.

12 + 5 13


 ## .NET SDK

6 14 7 15


 ### [8.0.4xx] `dotnet workload restore` with a workload set configured in the global.json will not work

Original file line number Diff line number Diff line change


 @@ -2,6 +2,14 @@

2 2 3 3


 You may encounter the following known issues, which may include workarounds, mitigations, or expected resolution timeframes.

4 4 5

+
 ## ASP.NET

6 + 7

+
 ### [9.0.6] Breaking Change: UseForwardedHeaders middleware now always checks ForwardedHeadersOptions.KnownNetworks and ForwardedHeadersOptions.KnownProxies

8 + 9

+
 `UseForwardedHeaders` middleware now always checks `ForwardedHeadersOptions.KnownNetworks` and `ForwardedHeadersOptions.KnownProxies`. Because both `KnownNetworks` and `KnownProxies` default to Loopback this means deployed applications may fail to apply `X-Forwarded-*` headers resulting in properties like scheme and host not being updated which can have side-effects e.g. `UseHttpsRedirection()` might always see http and always redirecting the request.

10 + 11

+
 The recommended fix is to set the `KnownNetworks` and `KnownProxies` values to the appropriate values. See https://learn.microsoft.com/aspnet/core/host-and-deploy/proxy-load-balancer for more details on using proxies and `UseForwardedHeaders()`. Alternatively, if you are fine accepting `X-Forwarded-*` headers from any source, which introduces security vulnerabilities, you can clear the `KnownNetworks` and `KnownProxies` properties.

12 + 5 13


 ## .NET WPF

6 14 7 15


 ### 1. Usage of incorrect types as DynamicResource

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4