You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An F3 sidecar uses the hosting Forest node as EC backend via RPC calls, we could reduce response size and latency of the RPC calls by using content compression.
Completion Criteria
Forest RPC server should support Accept-Encoding header (e.g. Accept-Encoding: gzip, deflate, compress, br, zstd) and respond with Content-Encoding header. (e.g. Content-Encoding: br)
RPC client in f3-sidecar should request content compression by sending Accept-Encoding header
confirmed that http.client sets Accept-Encoding: gzip and decodes gzipped response automatically
Consider using content compression in RPC parity tests
Summary
An F3 sidecar uses the hosting Forest node as EC backend via RPC calls, we could reduce response size and latency of the RPC calls by using content compression.
Completion Criteria
Accept-Encoding
header (e.g.Accept-Encoding: gzip, deflate, compress, br, zstd
) and respond withContent-Encoding
header. (e.g.Content-Encoding: br
)Accept-Encoding
headerconfirmed that
http.client
setsAccept-Encoding: gzip
and decodes gzipped response automaticallyAdditional Links & Resources
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Encoding
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding
The text was updated successfully, but these errors were encountered: