Bits of .NET

Have you ever tried to read the HttpContext.Request.Body in a middleware or a filter, only to find that your API controller receives an empty body? Or worse, your application crashes?

By default, the request body is a forward-only stream. Once it’s read, the pointer reaches the end, and there’s nothing left for the next component in the pipeline. Let’s fix this “one-time-only” problem.

❌ The Problem: Empty Streams and Crashes

If you read the stream directly, the position remains at the end of the stream:

// Reading like this "drains" the stream
var body = await reader.ReadToEndAsync(); 

// Next component gets nothing!

✅ The Fix: Enable Buffering

To read the request body multiple times, you must tell ASP.NET Core to buffer the stream. This allows the stream to be seekable, meaning we can reset its position to the beginning.

// Call this before reading the stream
context.Request.EnableBuffering();

// Reset position so the next component can read it from the start
context.Request.Body.Position = 0;

Why is this a Life-Saver?

• Custom Logging: You can log the incoming JSON payload without breaking the API controller.
• Request Validation: You can inspect the body in a Custom Middleware for security checks.
• Compatibility: It ensures that your Audit Logs don’t result in 400 Bad Request errors due to empty bodies.

💡 Pro Tip: Leave No Trace

Always wrap your manual reading logic in a try-finally block or ensure Position = 0 is called before _next(context). The rest of the pipeline should never know you were there!