ASP.NET Core middleware not executing in the correct order - how to debug?
I'm working on a personal project and This might be a silly question, but I'm working on an ASP.NET Core 5.0 application where I've implemented several middleware components. However, I'm working with an scenario where the middleware that logs requests is not executing before the authentication middleware, which leads to inconsistent logging behavior. I've tried rearranging the order of the middleware in the `Configure` method, but it seems the logging still occurs post-authentication. Here’s the relevant part of my `Startup.cs` file: ```csharp public void Configure(IApplicationBuilder app, IWebHostEnvironment env) { if (env.IsDevelopment()) { app.UseDeveloperExceptionPage(); } else { app.UseExceptionHandler("/Home/behavior"); app.UseHsts(); } app.UseHttpsRedirection(); app.UseStaticFiles(); // This logging middleware app.Use(async (context, next) => { Console.WriteLine($"Request URL: {context.Request.Path}"); await next(); }); // Authentication middleware app.UseAuthentication(); app.UseRouting(); app.UseAuthorization(); app.UseEndpoints(endpoints => { endpoints.MapDefaultControllerRoute(); }); } ``` The expectation is that requests should be logged before any authentication logic is applied. When I run the application, I get the following output in the console: ``` Request URL: /Home/Privacy ``` However, when I check the authentication logs, I see requests that are logged only after authentication succeeds. Has anyone encountered this scenario? Is there a way to ensure that my logging middleware executes before the authentication middleware, or is there something specific about the ASP.NET Core pipeline that I'm missing? Any insights or best practices would be greatly appreciated! I'm working on a CLI tool that needs to handle this. Is there a better approach? I recently upgraded to Csharp latest. Is this even possible?