We are seeing the same issue as described in ticket #101. When we apply the proposed solution (change the order of the middlewares), the error stops occurring, but the redirects and custom providers stop working instead.
It seems there was a similar issue that was fixed in #24, but that fix was for HttpContextExtensions.SetStatusCode, not HttpContextExtensions.Redirect.
Shouldn't the Redirect method in HttpContextExtensions
also check context.Response.HasStarted?
We are seeing this in both version 5 and 6
We are seeing the same issue as described in ticket #101. When we apply the proposed solution (change the order of the middlewares), the error stops occurring, but the redirects and custom providers stop working instead.
It seems there was a similar issue that was fixed in #24, but that fix was for
HttpContextExtensions.SetStatusCode, notHttpContextExtensions.Redirect.Shouldn't the
Redirectmethod in HttpContextExtensionsalso check
context.Response.HasStarted?We are seeing this in both version 5 and 6