Request.Body.Peeker 1.1.0

.NET Standard 2.0
dotnet add package Request.Body.Peeker --version 1.1.0
NuGet\Install-Package Request.Body.Peeker -Version 1.1.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Request.Body.Peeker" Version="1.1.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Request.Body.Peeker --version 1.1.0
#r "nuget: Request.Body.Peeker, 1.1.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Request.Body.Peeker as a Cake Addin
#addin nuget:?package=Request.Body.Peeker&version=1.1.0

// Install Request.Body.Peeker as a Cake Tool
#tool nuget:?package=Request.Body.Peeker&version=1.1.0

Peeking at HttpContext.Request.Body, without consuming it


Install it from Nuget

Check out the source code from Github

Install-Package Request.Body.Peeker -Version 1.0.0

After installation you can read the HttpContext request body without consuming it as follows

//Return string
var request = context.HttpContext.Request.PeekBody();

//Return in expected type
LoginRequest request = context.HttpContext.Request.PeekBody<LoginRequest>();

//Return in expected type asynchronously
LoginRequest request = await context.HttpContext.Request.PeekBodyAsync<LoginRequest>();

We are happy with the .Net core's Middlewares and ActionFilters. They provide us with a moment with the HTTP request to check the JWT validity or ApiKey with ease but as far as the parameters which we are interested are located in the HTTP header or the query string. As soon as we need to check a value in the request body we start facing some weird issues.

A stream is like a one-time message, it will be gone, as soon as you read it.

The HttpContext.Request.Body is also a stream, by reading it in middleware 1 , you will end up with an empty stream in the MVC middleware if the pipeline's order is as follows :

Middleware 1 -> MVC Middleware

The known solution is to read the stream and then put back in its place.

var request = HttpContext.Request;
var buffer = new byte[Convert.ToInt32(request.ContentLength)];
request.Body.Read(buffer, 0, buffer.Length);

By enabling the buffering mode on the HttpContext request body stream we can read the cloned version of the stream from the memory. After we have finished with the reading we must set the stream position pointer to the beginning again like this

request.Body.Position = 0;

Writing all above code, or having a helper class in each project to take care of it can be annoying. That's why i have put together a Nuget extension to the HttpRequest class to take care of all this behind the scene.

Install it from Nuget

Check out the source code from Github

Happy coding.

Product Versions
.NET net5.0 net5.0-windows net6.0 net6.0-android net6.0-ios net6.0-maccatalyst net6.0-macos net6.0-tvos net6.0-windows net7.0 net7.0-android net7.0-ios net7.0-maccatalyst net7.0-macos net7.0-tvos net7.0-windows
.NET Core netcoreapp2.0 netcoreapp2.1 netcoreapp2.2 netcoreapp3.0 netcoreapp3.1
.NET Standard netstandard2.0 netstandard2.1
.NET Framework net461 net462 net463 net47 net471 net472 net48 net481
MonoAndroid monoandroid
MonoMac monomac
MonoTouch monotouch
Tizen tizen40 tizen60
Xamarin.iOS xamarinios
Xamarin.Mac xamarinmac
Xamarin.TVOS xamarintvos
Xamarin.WatchOS xamarinwatchos
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.1.0 36,626 2/5/2021
1.0.1 2,767 6/15/2020
1.0.0 1,683 6/13/2020

support generic parsin , async , sync