Support q-factor weighting in Accept
header
#5966
Labels
meta-feature-request
Issues to track feature requests.
Accept
header
#5966
Problem description
At the moment, Lodestar does not support q-factor weighting in
Accept
header values.The following value results in JSON response but it should be SSZ due to higher weight
The reason for this is that a strict equality check is used on the raw header value to determine the response type and if the value does not exactly match
application/octet-stream
is will always send a JSON response.lodestar/packages/api/src/beacon/routes/debug.ts
Line 154 in 8794025
This can cause issues when using attestantio client as fetching the state as JSON is a lot slower and without increasing the max heap limit will crash Lodestar for a lot of networks, e.g. mainnet or holesky.
Solution description
Support q-factor weighting in
Accept
headerAdditional context
The text was updated successfully, but these errors were encountered: