Is your feature request related to a problem? Please describe.
I'm always frustrated when we're signing more things than actually needed. While we no longer need origin signature since #402 we still have two other left and there are zero reasons for that.
Describe the solution you'd like
API 2.26 should bring a new signature field that would sign serialized representation of both body and meta header (sequentially). It can be a replacement for RequestVerificationHeader (preferred) or a field inside of it. Of course we're keeping compatibility so old header is still accepted and checked for old requests.
Describe alternatives you've considered
I don't have any.
Is your feature request related to a problem? Please describe.
I'm always frustrated when we're signing more things than actually needed. While we no longer need origin signature since #402 we still have two other left and there are zero reasons for that.
Describe the solution you'd like
API 2.26 should bring a new signature field that would sign serialized representation of both body and meta header (sequentially). It can be a replacement for
RequestVerificationHeader(preferred) or a field inside of it. Of course we're keeping compatibility so old header is still accepted and checked for old requests.Describe alternatives you've considered
I don't have any.