During that read, we log what the response was as well as create a new stream (which hasn't been read yet) and return that new stream to the client. The reason for the creation of a dummy MemoryStream is that the response stream can only be read once. Finally, copy the dummy MemoryStream (containing the actual response) into the original stream, which gets returned to the client.Then, wait for the server to return a response.Next, create a dummy MemoryStream to load the new response into.First, read the request and format it into a string.I'll summarize the steps this piece of middleware accomplishes like this:
#ASP NET MVC LOG USER ACTIVITY AUDIT CODE#
Return the string for the response, including the status code (e.g. We need to reset the reader for the response so that the client can read it. String text = await new StreamReader(response.Body).ReadToEndAsync() We need to read the response stream from the beginning. Private async Task FormatResponse(HttpResponse response) First off, let's create a new Employee class with a few properties: public class Employee In order to make this demo, we'll need to create a few dummy classes. This project and post were originally written for ASP.NET Core 2.1, but both have been updated to.
NET 5.0 the simplest way to do this was using middleware.Ĭome along with me as we build a piece of middleware that automatically records requests and responses! The Sample ProjectĪs with many of my code-heavy posts, this one has a sample project over on GitHub. In any case, I needed a way to record requests and responses, and in. Though, hopefully, with a bit more modern technology. One of our requirements for this project was that, because this API would be used by a great many different apps with different loads, we wanted to be able to record requests to and responses from this API, similarly to how a court stenographer (aka court reporter) records all questions from lawyers and responses from defendants. NET 5.0 to the wider world has given me the opportunity to dive deeper into some of its features while building an app that will be used in the real world, a rare opportunity I'm loathe to waste.
0 kommentar(er)
