-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON-RPC endpoint does not accept []-enclosed requests #169
Comments
Lotus does not support batched requests either -- but they have less need to because the Filecoin network has other explorers, and this isn't a popular feature in general (esp. when both the client and server support WebSockets as a transport). However, it should be easy to implement here. Ideally we'd want to handle individual requests in parallel, with some limit to prevent attacks. |
@raulk We already have a fix in consensus-shipyard/fendermint#395. Fwiw, this is not even a batched request; it's just formatted as such. It might be enough to accept said formatting, but we'll see what other surprises blockscout has in store (inc. actual batched requests, maybe). |
@jsoares I'd expect to find multiple requests when loading listing and detail pages, or when indexing blocks and transactions. I suspect the explorer became blocked here and we didn't get to see further, more elaborate requests. |
Indeed, that's what I expect too. That and tracing... |
The fix works and allows for batch requests. New issues in #168. |
Issue type
Bug
Have you reproduced the bug with the latest dev version?
Yes
Version
dev
Custom code
No
OS platform and distribution
No response
Describe the issue
While trying to deploy blockscout, I met the following error:
This seems to be caused by those array brackets [ ] surrounding the body. Turns out that blockscout formats every request as batched, and we don't support it.
Without [ ]
With [ ]
On the contrary, both work fine with public ethereum endpoints, e.g.
This may break compatibility with other ethereum tooling.
Repro steps
Run curl above against a fendermint eth rpc.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: