Phalcon\Http\Request::getRawBody() empties the raw body content

[mapsi]

Hello y'all,

Since v1.2.1 Phalcon\Http\Request::getRawBody() empties the raw body content.

What does this mean?
If from a terminal I fire ...

curl -XGET 'http://server/controller/action' -d '{"query":[["george","alan", "thomas"]]}'

and in my application I have ...

var_dump($app->request->getRawBody(), $app->request->getRawBody());exit;

In Phalcon v1.2.0 I would get ...

string(37) "{"query":["george","alan","thomas"]]}"
string(37) "{"query":["george","alan","thomas"]]}"

In Phalcon v1.2.1+ I get ...

string(37) "{"query":["george","alan","thomas"]]}"
string(0) ""

and this stands true for available all post v1.2.0 versions.

As this is not a documented feature, I can only assume it's bug.

If I remember correctly, I read somewhere that the JSON library has been changed in the post v1.2.0 versions so maybe this is the cause of the issue?

Many thanks in advance,
Angel

[dreamsxin]

Because you use the GET, the first data read from the stream, the second stream has no data, and if you use POST is no problem, because the POST data has been read, will stored in SG (request_info). Raw_post_data.

In Phalcon 1.2.0，Use the property _rawBody to store the data.

I do not know better that way, and so @phalcon to answer.

[ghost]

That's not a JSON bug, this is my fault. I did not assume that you will try to access raw POST data in GET request and this is why one property was optimized away.

I'll try to revert back the original behavior

[phalcon]

This was fixed in #1091