IHttpContextAccessor HttpContext are always null

Question

I have problem when I'm trying to get httpcontext from IHttpContextAccessor field is always null.

There is my startup.cs

    public void ConfigureServices(IServiceCollection services)
    {
        // Add framework services.
        services.AddMvc();
        services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();
    }

    public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
    {
        .....

        // This is always null
        var httpContext = app.ApplicationServices.GetService<IHttpContextAccessor>().HttpContext;

        .....
    }

Configure runs as the app is starting, not per request. – ssmith Jun 04 '17 at 16:25 — ssmith, Jun 04 '17 at 16:25

Set · Accepted Answer · 2017-06-03T11:23:47.583

27

You always will have null HttpContext in Configure method.

This method is used to specify how the ASP.NET application will respond to HTTP requests and calls once on Application start, not for each HTTP request. That's why there is nothing, what could be populated to HttpContext.

You need to pass IHttpContextAccessor in your service classes and call IHttpContextAccessor.HttpContext during request processing. You may look into "similar" situation with getting HTTP context in this SO post.

edited Jun 03 '17 at 11:23

answered Jun 03 '17 at 11:18

Set

47,577
22
132
150

Mine is null in a controller method – jjxtra Mar 05 '23 at 06:21

score 0 · Answer 2 · answered May 13 '22 at 01:14

In my case the problem was I forget await in the begining of stack, explicity in my constructor action method

NOTE: Using net core 5.0 with IHttpContextAccessor

So the problem was in the next code...

[HttpPost]
public async Task AnyAction()
{
    await service.MethodReturningTask(); //await was not
}

DETAIL: The method "MethodReturingTask()" had some await in their implementations, and after that await the stack disapear together with httpContextAccessor.HttpContext propertie (to null)

score 0 · Answer 3 · answered Feb 20 '23 at 05:28

0

In my case, this error appeared for a while during debugging when I commented JwtAuth attribute on my controller. So, make sure you're sending jwt token with that attribute applied.

answered Feb 20 '23 at 05:28

zed101

193
1
2
10

IHttpContextAccessor HttpContext are always null

3 Answers3