Anders Mörner

I'd suggest forking the repository and setting up a small unit test that replicated your error. Then you can debug through the serialization and see where it goes wrong.

Hmm... If the problem truly lies in `ReadMessageAsync` you could try to asynchronously copy the content of stream to a memorystream up top and use that instead. That will result...

> you mean like the PR i created? Yes. Can you test your service with the new code and see if that helped with your performance issues?

> Also meaning to ask, is there any thing that logs request body only if its bad request or something? Nope. It's certainly possible to do that in a middleware...

In asp.net core it's left out by design for performance reasons but it is set in WriteMessageAsync, as you've noted. I have never checked for it myself, so I don't...

A new nuget package is on its way now

I’ll try to get this sorted later tonight

The new nuget package should be available now

Please fix the build errors in the test project and I will take a look. I would also like you to add a test case to make sure that it...

And thank you for the PR 😄