如何将ASP.NET Framework配置迁移到ASP.NET Core? [英] How to migrate ASP.NET Framework configurations to ASP.NET Core?

问题描述

我正在将IIS上托管的ASP.NET Framework应用程序迁移到Kestrel上托管的ASP.NET Core.

I'm migrating an ASP.NET Framework application hosted on IIS to ASP.NET Core hosted on Kestrel.

在ASP.NET Framework中，我有一个web.config，其中包含数十种自定义配置/优化，例如:

In ASP.NET Framework, I have a web.config with dozens of custom configurations/optimizations, like:

<httpRuntime executionTimeout="120" maxUrlLength="8192" maxQueryStringLength="8192" />

问题是我找不到如何配置这些设置，例如带有Kestrel的ASP.NET Core中的 maxQueryStringLength .

Problem is that I can't find how to configuration those settings, like maxQueryStringLength in ASP.NET Core with Kestrel.

例如，在此 answer 中，用户说它在ASP.NET Core中不可用，建议您这样做.使用IIS或NGINX.

For example, in this answer, the user says that it is not available in ASP.NET Core and recommends to use IIS or NGINX.

如何在不使用ASP.NET Core中的 web.config 文件的情况下迁移我的 web.config 设置?我希望使用默认的 appsettings.json 文件.

How can I migrate my web.config settings without using a web.config file in ASP.NET Core? I would prefer to use the default appsettings.json file.

推荐答案

您可以使用ASP.NET Core Kestrel限制进行适当的配置

You may use ASP.NET Core Kestrel limits to make the appropriate configs

https://docs.microsoft.com/zh-cn/dotnet/api/microsoft.aspnetcore.server.kestrel.core.kestrelserverlimits?view=aspnetcore-3.1

可以通过Program.cs中的配置完成

It could be done via configs in Program.cs

#elif Limits
        public static void Main(string[] args)
        {
            CreateHostBuilder(args).Build().Run();
        }

        public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)
                .ConfigureWebHostDefaults(webBuilder =>
                {
                    #region snippet_Limits
                    webBuilder.ConfigureKestrel(serverOptions =>
                    {
                        serverOptions.Limits.MaxConcurrentConnections = 100;
                        serverOptions.Limits.MaxConcurrentUpgradedConnections = 100;
                        serverOptions.Limits.MaxRequestBodySize = 10 * 1024;
                        serverOptions.Limits.MinRequestBodyDataRate =
                            new MinDataRate(bytesPerSecond: 100, 
                                gracePeriod: TimeSpan.FromSeconds(10));
                        serverOptions.Limits.MinResponseDataRate =
                            new MinDataRate(bytesPerSecond: 100, 
                                gracePeriod: TimeSpan.FromSeconds(10));
                        serverOptions.Listen(IPAddress.Loopback, 5000);
                        serverOptions.Listen(IPAddress.Loopback, 5001, 
                            listenOptions =>
                            {
                                listenOptions.UseHttps("testCert.pfx", 
                                    "testPassword");
                            });
                        serverOptions.Limits.KeepAliveTimeout = 
                            TimeSpan.FromMinutes(2);
                        serverOptions.Limits.RequestHeadersTimeout = 
                            TimeSpan.FromMinutes(1);
                    })
                    #endregion
                    .UseStartup<Startup>();
                });
#elif Port0

红est选项也可以使用配置提供程序进行设置.例如，文件配置提供程序( https://docs.microsoft.com/zh-cn/aspnet/core/fundamentals/configuration/?view=aspnetcore-3.1#file-configuration-provider )可以从appsettings.json或appsettings.{Environment} .json文件:

Kestrel options can also be set using a configuration provider. For example, the File Configuration Provider ( https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-3.1#file-configuration-provider ) can load Kestrel configuration from an appsettings.json or appsettings.{Environment}.json file:

{
  "Kestrel": {
    "Limits": {
      "MaxConcurrentConnections": 100,
      "MaxConcurrentUpgradedConnections": 100
    },
    "DisableStringReuse": true
  }
}

此外，如果您需要通过代码来管理这些事情，则可以尝试通过中间件来处理

Also, if you need to manage these things via code you may try to handle it via middleware

public class RequestFilterMiddleware
    {
        private readonly RequestDelegate _next;
        private const long _allowedRequestQueryStringMaxLength = 100;
        private const long _allowedUrlStringMaxLength = 100;
        public RequestFilterMiddleware(RequestDelegate next)
        {
            _next = next;
        }

        public async Task Invoke(HttpContext httpContext)
        {
            var queryStringLength = httpContext.Request.QueryString.Value?.Length;
            if (queryStringLength > _allowedRequestQueryStringMaxLength)
            {
                //throw exception or send some appropriate http status code
            }

            var urlRequestLength = httpContext.Request.GetDisplayUrl().Length;
            if (urlRequestLength > _allowedUrlStringMaxLength)
            {
                //throw exception or send some appropriate http status code
            }

            using (var TokenSource = System.Threading.CancellationTokenSource.CreateLinkedTokenSource(httpContext.RequestAborted))
            {
                httpContext.RequestAborted = TokenSource.Token;
                var DelayTask = Task.Delay(500, TokenSource.Token);
                var NextTask = _next.Invoke(httpContext);
                if (await Task.WhenAny(DelayTask, NextTask).ConfigureAwait(false) == DelayTask)
                {
                    //LogStuff for long running requests
                   
                }
                TokenSource.Cancel();
            }

            await _next(httpContext);
        }
    }

不幸的是，此刻Kestrel中没有超时选项，要获取更多信息，您可以阅读此主题

Unfortunately, the timeout option is not available in Kestrel at this moment, to get more information you may read this topic https://github.com/dotnet/aspnetcore/issues/10079

但是，至少可以将长期运行的请求记录在生产中，以供以后的优化之用.

However, it's possible at least to log long running requests in production for later optimization purposes.

这篇关于如何将ASP.NET Framework配置迁移到ASP.NET Core?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！