Hello,
I pushed a fix to master and 4.2 branches -- in the first request you tried, the jsonrpc field was integer 2, according to specs it must be the string "2.0" (http://www.jsonrpc.org/specification#request_object).
For the other requests, I didn't get a crash. id field is ok to be string or int or missing.
Cheers, Daniel
On 07/01/15 09:01, Alex Balashov wrote:
On the other hand, I can't seem to get it to crash if I send fully-formed requests like this one:
POST /csrp_rpc/ HTTP/1.1 Content-Type: application/json Content-Length: 54 Call-ID: 13d40122621463619e0c14a1f1dad01a Host: 172.30.110.4:5060 Connection: close
{"jsonrpc":"2.0","id":"ef8e1","method":"core.version"}
... so, there's something amiss here.