Pass response contexts from RPC middleware to HTTP middleware

[shunsukew]

I am developing a rate-limiting RPC middleware. Currently, jsonrpsee framework utilizes MethodResponse Extensions in the RPC layer and http::Response Extensions in the HTTP layer, with these extensions operating independently of each other.

I would like to propagate context information from the RPC layer to the HTTP layer to achieve functionality such as returning a status code other than 200 (429 in my case) or, at the very least, adding an HTTP header to indicate rate limiting based on data in contexts.

What would be the best approach to transfer context (Extensions) information from a jsonrpsee RPC middleware to a hyper HTTP middleware?

[niklasad1]

I think we could copy the extensions from the MethodResponse to the HTTP response to fix that and then you would need some HTTP middleware to check whether some error occurred and set desired HTTP status code on the response.

This shouldn't be that hard to fix

[shunsukew]

That would be really helpful. Thank you so much.
A single RPC call functions as expected, however, batch responses may require merging extension data. Addressing potential conflicts of the same Type data across calls within a batch is a subject for discussion.