Converting OwinHttpRequestContext to HttpContext? (IHttpHandler and websockets)

Question

I am trying to implement web sockets in my application that currently implements a RESTful web API. I want certain pieces of information to be able to be exposed by a web socket connection so I am trying to figure out how to upgrade a normal HTTP request to a web socket connection.

I am trying to follow this tutorial

The problem I am having is my controller that handles the Get request inherits from ApiController and I am trying to do this:

 if (HttpContext.Current.IsWebSocketRequest)
    {
        HttpContext.Current.AcceptWebSocketRequest(SomeFunction);
    }
    return new HttpResponseMessage(HttpStatusCode.SwitchingProtocols);

The problem is my HttpContext.Current is always null and I do not know why. It seems like there is no such thing as a HttpContext. I do see however from the request that comes in that their is a HttpRequestContext that comes in with the request. Are these two objects related at all and is there any way I can get access to the .IsWebSocketRequest method so I can try and upgrade the request to a web socket connection?

My controller and what I am trying to do:

    [HttpGet]
    public HttpResponseMessage GetSomething()    
    {
        if (HttpContext.Current.IsWebSocketRequest()){
             Console.WriteLine("web socket request..");  
        }
    }

^ HttpContext.Current is always null. My controller inherits solely from ApiController

My thought was that maybe when the request comes in it may create a new thread for that specific request which is why it could be null. This is a project I just joined so I am not sure for sure. — user3037172, Jun 08 '15 at 02:56
Could you show the code for the full controller? We are using Web API and connecting very similar to your code and HttpContext.Current is not null. Also, are you customizing the controller selection? It's possible there is some custom code that is putting it on a background thread like @Asad mentioned or it could be re-using controllers rather than instantiating a new one. — ManOVision, Jun 08 '15 at 05:45

score 3 · Answer 1 · answered Jun 10 '15 at 13:49

3

To get access to the Httpcontext in a MVC ApiController use this code.

        if (Request.Properties.ContainsKey("MS_HttpContext"))
        {
            HttpContextWrapper HttpContext = (HttpContextWrapper)Request.Properties["MS_HttpContext"];
            if (HttpContext != null)
            {
                if (HttpContext.IsWebSocketRequest)
                {
                    HttpContext.AcceptWebSocketRequest(SomeFunction);
                }
            }
        }

This will get the HttpContext out of the Request if it is supplied.

answered Jun 10 '15 at 13:49

Brian from state farm

2,825
12
17

2

It does not contain "MS_HttpContext". The ones I see under Request.Properties are "MS_OwinContext", "MS_RequestContext", "MS_HttpConfiguration", "MS_RoutingContext", "MS_HttpRouteData" and some others – user3037172 Jun 11 '15 at 12:59
Do you have a reference to System.Web? If not try adding that to your project. – Brian from state farm Jun 11 '15 at 18:16
Doesn't change a thing. Have System.Web.Http. – user3037172 Jun 12 '15 at 21:02
Are you running in a separate thread? See http://stackoverflow.com/questions/8109526/the-cross-thread-usage-of-httpcontext-current-property-and-related-things – Brian from state farm Jun 16 '15 at 13:12

Converting OwinHttpRequestContext to HttpContext? (IHttpHandler and websockets)

1 Answers1