Seungbae Yu 38e002f464 rpc: check that "version" is "2.0" in request objects (#25570) ... The JSON-RPC spec requires the "version" field to be exactly "2.0", so we should verify that. This change is not backwards-compatible with sloppy client implementations, but I decided to go ahead with it anyway because the failure will be caught via the returned error.		2022-09-02 17:47:29 +02:00
..
invalid-badid.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
invalid-badversion.js	rpc: check that "version" is "2.0" in request objects (#25570)	2022-09-02 17:47:29 +02:00
invalid-batch.js	rpc: fix issue with null JSON-RPC messages (#21497)	2020-08-28 16:27:58 +02:00
invalid-idonly.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
invalid-nonobj.js	rpc: fix issue with null JSON-RPC messages (#21497)	2020-08-28 16:27:58 +02:00
invalid-syntax.json	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
reqresp-batch.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
reqresp-echo.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
reqresp-namedparam.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
reqresp-noargsrets.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
reqresp-nomethod.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
reqresp-noparam.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
reqresp-paramsnull.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
revcall.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
revcall2.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00
subscription.js	rpc: implement full bi-directional communication (#18471)	2019-02-04 13:47:34 +01:00