Home/ Questions/Q 8226477
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T15:47:05+00:00

I’m working on a self-hosted ASP.NET web api-application. Everything works fine, but now I’m

  • 0

I’m working on a self-hosted ASP.NET web api-application.
Everything works fine, but now I’m struggling with HttpContext:

I need to save session-informations from the client.
But HttpContext.Current is always null.
So it’s obvious that my HttpSelfHostServer don’t work with the static HttpContext-Class.

The thing I don’t understand is: why..?
And I can’t figure out a way to tell neither HtttpSelfHostServer nor HttpSelfHostConfiguration to work with HttpContext.

Here’s what I’m doing:

  1. Creating a HttpSelfHostConfiguration

    • 1.1 Adding Service-Resolvers & Routes
    • 1.2 Adding custom UserNamePassword-Validator

  2. create new Instance of HttpSelfHostServer with the config

    • 2.1 server.OpenAsync().Wait()

Any help how I can tell my server to work with HttpContext.Current is greatly appreciated!
Cheers!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You won’t be able to use HttpContext in a self-hosted environment. HttpContext is set by the ASP.Net pipeline, which you won’t have if you don’t run under IIS/ASP.Net.

    The HttpContext is only available in the Web-Hosting mode, in which the HttpControllerHandler creates the request.

    FYI- I invite you to read the following great articles from Pedro Felix to better understand the different hosting models:

    • 0