Non-form-encoded bodies should not be parsed as though they are form encoded.
When a non-form-encoded content-type is present, the body in Request should not be parsed as though it is form-encoded.
Here is the fix with test: http://github.com/nrstott/jack/commit/fcb1b1f0a57c67c43c8c342dc8e34e93b25fa369
I'd like to see this fixed as well. I think the title of the ticket could be more generally "Non-form-encoded bodies should not be parsed as though they are form encoded."
I had trouble with the same some time ago because I couldn't rewind the body to get at the (non-form-encoded) content.
I liked your suggestion for a title, so I changed the title of the ticket.
It is fixed in my repo, so pull from me if you need it before Tom has time to integrate it into master