Checkpointz should handle this as prefer sending ssz response and if not suppored fall back to json and if that is not supported as well it should return a 406 status code.
The current behavior is that it assumes the client requested json data and it results in the following response for getStateV2
unsupported content-type: application/json
And it returns a 415 status code (406 would be more correct).
Ideally, should follow RFC-9110 for Accept header handling.
We have a bunch of test cases in Lodestar which might help to test the implementation, see acceptHeader.test.ts
At the moment, Checkpointz does not support q-factor weighting in
Acceptheader values.E.g. if a client sends a header like this
Checkpointz should handle this as prefer sending ssz response and if not suppored fall back to json and if that is not supported as well it should return a 406 status code.
The current behavior is that it assumes the client requested json data and it results in the following response for getStateV2
And it returns a 415 status code (406 would be more correct).
Ideally, should follow RFC-9110 for Accept header handling.
We have a bunch of test cases in Lodestar which might help to test the implementation, see acceptHeader.test.ts