WebApi2 and Session State - has something changed?
We have an ASP.NET MVC5 web application (not core!), that has both regular controllers and WebApi controllers. We refer to HttpContext.Current.* in order to do caching in some of those WebApi controller endpoints.
This has worked for us for a long time, no problems. But recently, perhaps after updating some of the MVC and WebApi related packages, Http.Current is sometimes null when we try to access it from the WebApi controller. I have tried many of the things suggested if you google this kind of issue, such as setting the SessionStateBehavior and so on, to no avail.
Has something changed regarding this recently?
0 comments:
Post a Comment