in #3234 we provided a way to access Router service level requests and responses. At this step, the body is a stream of byte chunks, with no real guarantee about the format:

• it could be JSON, or something else
• it could be multipart, but not neatly cut at the multipart header (the rrouter service enforces that, but a plugin might change it)
• it could be encoded in something else than UTF8
• it could be compressed
• chunks can have arbitrarily high latency between them

Due to these issues, we do not give access to the body, until we can provide a good API to manipulate it