huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Remove obsolete Azure ForwardedHeaders workaround. (#359)

This commit is contained in:
Chris R 2017-04-21 19:02:11 -07:00 committed by GitHub
parent ce3c71b5b3
commit b7ed993d9d
1 changed files with 0 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/Microsoft.AspNetCore.Server.IISIntegration/WebHostBuilderIISExtensions.cs
View File

@ -57,13 +57,6 @@ namespace Microsoft.AspNetCore.Hosting
services.Configure<ForwardedHeadersOptions>(options => services.Configure<ForwardedHeadersOptions>(options =>
{ {
options.ForwardedHeaders = ForwardedHeaders.XForwardedFor | ForwardedHeaders.XForwardedProto; options.ForwardedHeaders = ForwardedHeaders.XForwardedFor | ForwardedHeaders.XForwardedProto;
// https://github.com/aspnet/IISIntegration/issues/140
// Azure Web Sites needs to be treated specially as we get an imbalanced set of X-Forwarded-* headers.
// We use the existence of the %WEBSITE_INSTANCE_ID% environment variable to determine if we're running
// in this environment, and if so we disable the symmetry check.
var isAzure = !string.IsNullOrEmpty(Environment.GetEnvironmentVariable("WEBSITE_INSTANCE_ID"));
options.RequireHeaderSymmetry = !isAzure;
}); });
}); });
} }