Shulou(Shulou.com)06/01 Report--

This article mainly explains "how to set up conditional access routes for ASP.NET Core". Friends who are interested may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to set up conditional access routing for ASP.NET Core.

1. Brief introduction

Sometimes, we may include requests with debugging capabilities in the Web API. For example, in our last article, why is the value of the ASP.NET Core database connection string different from that of appsettings.json? The function used to obtain configuration values:

Endpoints.MapGet ("/ test2/ {key:alpha}", async context = > {var key = context.Request.RouteValues ["key"] .ToString (); foreach (var provider in Configuration.Providers.Reverse ()) {if (provider.TryGet (key, out string value)) {await context.Response.WriteAsync (provider.ToString ()); await context.Response.WriteAsync ("\ r\ n") Await context.Response.WriteAsync (value); break;})

But you don't want to expose them in a production environment. To achieve this, there are several options:

User rights verification

Compiled to a separate dll and not released to the production environment

Each of these solutions has its own advantages and disadvantages. Here we introduce a simple scheme implemented using Middleware.

two。 Realize

As you can see from the figure above, in order to access the actual route, the request needs to go through Middleware. We can check it in the outermost Middleware. Only the request that meets the conditions can be passed, otherwise an error of 403 is returned.

The Middleware code is as follows:

Public class DebugMiddleware: IMiddleware {public async Task InvokeAsync (HttpContext context, RequestDelegate next) {var isDebugEndpoint = context.Request.Path.Value.Contains ("/ test"); var debugKey = context.Request.Query ["debugKey"] .ToString (); var debugKeyInConfig = "123456" / / from the configuration if (isDebugEndpoint & & debugKeyKeyInConfig) {context.SetEndpoint (new Endpoint ((context) = > {context.Response.StatusCode = StatusCodes.Status403Forbidden; return Task.CompletedTask;}, EndpointMetadataCollection.Empty, "No access")) } await next (context);}}

When the request address contains "/ test", check whether the request parameter debugKey is the same as the configured value, and return a 403 error if it is different.

The effect is as follows:

At this point, I believe you have a deeper understanding of "how to set up conditional access routing for ASP.NET Core". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.