ETH gateway RPC bug report

[sirormy]

I found that sending RPC request via cloudflare ETH gateway service, can got two different result.
For example, when I query some address’s balance:

curl --location --request POST 'https://cloudflare-eth.com/' \
--header 'Content-Type: application/json' \
--header 'Cookie: __cfduid=d827729942fe427213e65ab90098f0a221607488911' \
--data-raw '{"jsonrpc":"2.0","method":"eth_getBalance","params":["0x5b88bF5D0e6DC70B02e459C0127b53e2dAD4687D", "latest"],"id":1}'

I will got the two results:

{"jsonrpc":"2.0","id":1,"result":"0x0"}
{"jsonrpc":"2.0","result":"0x0","id":1}

the difference is the properties’ order, and the first one, it return the result and one more blank line,

in the swift ETH SDK, it will throw a parsing error, because it is not a strict json format, please check.

[sdayman]

@sirormy

please check.

I’m afraid the Community can’t open tickets for bug reports. Your best bet is to contact support.

To contact Cloudflare Customer Support, login & go to https://dash.cloudflare.com/?account=support and select get more help. If you receive an automatic response that does not help you, please reply and indicate you need more help.

[sirormy]

OK, Thanks