Prevent users from iterating a request's body after having responded to that request

[Joannis]

Currently, we implement an HBRequest's Body with the NIOAsyncChannel's inbound. This is efficient, but might lead to users escaping the request.body for later consumption. This will lead to bugs.

[adam-fowler]

Are you talking about iterating the request body in an unstructured task?

[Joannis]

Exactly, but explicitly after the response was already returned

[adam-fowler]

You could set the request body to have been iterated as soon as the response body has finished writing. So any subsequent attempts to iterate via an unstructured task will fail and provide a better indication as to why it failed.