Aug 19, 2014 at 7:30 PM
Edited Aug 19, 2014 at 7:31 PM
We are receiving the following error hundreds of times a day after switching our authentication system to ASP .NET Identity:
Server cannot append header after HTTP headers have been sent
The error has been discussed in great detail here:
The issue appears to be in Microsoft.Owin.Host.SystemWeb and the solution appears to be to remove the dependency on Microsoft.Owin.Host.SystemWeb until some future version of .NET framework is able to fix the issue as described by the user "thatcher"
on Jul 31 at 8:15 AM.
My question is, how can I remove that dependency with ASP .NET Identity framework? It seems to rely on it in many places such as calling GetOwinContext() on the HttpContext object.
Thoughts on how to fix this Katana bug with ASP .NET Identity?