Parse the request body so it's easily usable by the user

[tomaka]

No description provided.

[tomaka]

The idea behind this issue, I think, is to handle Content-Encoding automatically.
(this has nothing to do with JSON/form-data/etc.)

[bretmattingly]

Do we have a realistic subset of MIME types we want to target with this? Without even considering the multimedia types (image/*, audio/*, video/*) there are a staggering amount of valid MIME types, and even a fair amount of common ones as well.

For reference, IANA listing of Media Types

[tomaka]

If I remember correctly why I opened this issue, this has absolutely nothing to do with MIME types.
I'm talking about chunked transfer encoding, gzip, etc.

Although in practice I'm not sure if it's even allowed for a client to send chunked or gzipped data in a request.

[bretmattingly]

Damn it. Not enough coffee. I saw your Content-Encoding and read Content-Type...You've even explicitly mentioned it.

I'll review some of the HTTP standard and see what I can determined about Content-Encoding