.NET Core 3+ solution with proper resource handling: Replace response stream by MemoryStream to prevent its sending. Return the original stream after the response is modified: public async Task Invoke(HttpContext context) { var response = context.Response; //uncomment this line to re-read context.Request.Body stream //context.Request.EnableBuffering(); var originBody = response.Body; using var newBody = new MemoryStream(); response.Body … Read more
I know that this is a pretty old post, but just in case if it helps someone, here’s a nuget package to perform Request Decompression in .net core https://github.com/alexanderkozlenko/aspnetcore-request-decompression
Okay, after some digging around and even more trial and error I’ve found answers to my questions and got everything to work. Here’s what I found: I am supposed to create a SharedResources.cs class, but where should i put it and should it be empty or do I need to fill it with some data? … Read more
Although this is an old thread, but since I stumbled with the same question recently I thought shedding some more light on the internals may benefit others The short answer is depends on your service type and your APIs. you don’t need to call UseAuthentication when: You implement your own middleware that handles authentication – … Read more
UserManager<ApplicationUser> is (by default) registered as a scoped dependency, whereas your CreateCompanyMiddleware middleware is constructed at app startup (effectively making it a singleton). This is a fairly standard error saying that you can’t take a scoped dependency into a singleton class. The fix is simple in this case – you can inject the UserManager<ApplicationUser> into … Read more
In my original response I had totally misread the question and thought the poster was asking how to read the Request.Body But he had asked how to read the Response.Body. I’m leaving my original answer to preserve history but also updating it to show how I would answer the question once reading it correctly. Original … Read more