Description:
------------
When sending JSON via php://input, my body was truncated at the point where it read <<<<<.  It seems that this signals php to stop reading in from php://input.  The JSON parse will fail since the truncation yields invalid JSON.  I'll send the JSON blob that causes the error via the patch file.  I remove the pattern /(<|>)+/ as a work around at the moment.

Here's where it fails:

d63da06809da5cf7c712":false},"is_super_like":false,"is_boost_match":false,"person":{"_id":"56c1d63da06809da5cf7c712","badges":[],"bio":"Why do guys put their height on here? Are we more compatible the taller we are? Let\'s test it:\\n\\n4\'10\\"\\nLibra\\nSarcastic\\nENFJ\\nType A\\nAmbitious\\nSapiosexual <<<<<<<<<<'

Pretty sure the <<<'s cause this.  Seems like the underlying stream processor has some sort of break condition dependent on the < symbols.

Test script:
---------------
POST something like {

<?php
$input = file_get_contents('php://input');
$j = json_decode(stripslashes(html_entity_decode($input)), true);
echo json_encode($j);
?>

Expected result:
----------------
All JSON data is received and retrievable via my $input variable for decoding.

Actual result:
--------------
JSON is truncated at an instance of '<<<<<<<<<<', rendering it invalid.