Heh. Whoops! What I meant was… Hmmm…

I don't think we should discourage this method *that* strongly. I think it's more of making the “most standard” method easier than it is discouraging the less standard method. `json` follows the standard to a T, refusing to even attempt to parse a request that isn't explicitly marked as JSON as such. But this isn't a security hole per se, in that we are about as certain as we are with any other part of the system that our JSON parser is secure.

That said, I do think `forcedBodyAsJson` is more descriptive of what's happening than just `bodyAsJson`. So I'm a little torn.