How to get HttpContext.Current in ASP.NET Core? [duplicate]

by

As a general rule, converting a Web Forms or MVC5 application to ASP.NET Core will require a significant amount of refactoring.

HttpContext.Current was removed in ASP.NET Core. Accessing the current HTTP context from a separate class library is the type of messy architecture that ASP.NET Core tries to avoid. There are a few ways to re-architect this in ASP.NET Core.

HttpContext property

You can access the current HTTP context via the HttpContext property on any controller. The closest thing to your original code sample would be to pass HttpContext into the method you are calling:

public class HomeController : Controller
{
    public IActionResult Index()
    {
        MyMethod(HttpContext);

        // Other code
    }
}

public void MyMethod(Microsoft.AspNetCore.Http.HttpContext context)
{
    var host = $"{context.Request.Scheme}://{context.Request.Host}";

    // Other code
}

HttpContext parameter in middleware

If you’re writing custom middleware for the ASP.NET Core pipeline, the current request’s HttpContext is passed into your Invoke method automatically:

public Task Invoke(HttpContext context)
{
    // Do something with the current HTTP context...
}

HTTP context accessor

Finally, you can use the IHttpContextAccessor helper service to get the HTTP context in any class that is managed by the ASP.NET Core dependency injection system. This is useful when you have a common service that is used by your controllers.

Request this interface in your constructor:

public MyMiddleware(IHttpContextAccessor httpContextAccessor)
{
    _httpContextAccessor = httpContextAccessor;
}

You can then access the current HTTP context in a safe way:

var context = _httpContextAccessor.HttpContext;
// Do something with the current HTTP context...

IHttpContextAccessor isn’t always added to the service container by default, so register it in ConfigureServices just to be safe:

public void ConfigureServices(IServiceCollection services)
{
    services.AddHttpContextAccessor();
    // if < .NET Core 2.2 use this
    //services.TryAddSingleton<IHttpContextAccessor, HttpContextAccessor>();

    // Other code...
}

More Related Contents:

  1. AddTransient, AddScoped and AddSingleton Services Differences
  2. How to read AppSettings values from a .json file in ASP.NET Core
  3. Return file in ASP.Net Core Web API
  4. Return View as String in .NET Core
  5. How to instantiate a DbContext in EF Core
  6. .NET Core DI, ways of passing parameters to constructor
  7. Automatic native and managed DLLs extracting from Nuget Package
  8. Send HTTP POST message in ASP.NET Core using HttpClient PostAsJsonAsync
  9. What are the costs and possible side effects of calling BuildServiceProvider() in ConfigureServices()
  10. Command dotnet ef not found
  11. Switch between dotnet core SDK versions
  12. Inject service into Action Filter
  13. Proper way to register HostedService in ASP.NET Core. AddHostedService vs AddSingleton
  14. How to set json serializer settings in asp.net core 3?
  15. Setting the version number for .NET Core projects – CSPROJ – not JSON projects
  16. System.Text.Json: Deserialize JSON with automatic casting
  17. File permissions on Linux/Unix with .NET Core
  18. How do I reference a .NET Framework project in a .NET Core project?
  19. Is there a built in way of using snake case as the naming policy for JSON in ASP.NET Core 3?
  20. Refresh Token using Polly with Named Client
  21. Using a Scoped service in a Singleton in an Asp.Net Core app
  22. Entity Framework Core: `SqlNullValueException: Data is Null.` How to troubleshoot?
  23. Dependency Injection with classes other than a Controller class
  24. Cannot find command ‘dotnet ef’
  25. How to get user information in DbContext using Net Core
  26. How should I manage DbContext Lifetime in MVC Core?
  27. ASP.NET Core modify/substitute request body
  28. Net Core: Execute All Dependency Injection in Xunit Test for AppService, Repository, etc
  29. What Nuget packages must be referenced by an ASP.NET Core 6 application parts project
  30. No service for type ‘Microsoft.AspNetCore.Identity.UserManager`1[Microsoft.AspNetCore.Identity.IdentityUser]’ has been registered

Leave a Comment