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
I'm trying to check that the signature verify result includes certain fields, for example on a POST with a body, the content-digest should be covered. I discovered that the keys in the VerifyResult covered_components OrderedDict are quoted; i.e., start and end with double-quote characters. Is this essential? The values are not double-quoted so I am wondering if maybe this was an oversight. Please see example:
Just one more thing, would you please use the verify result in the test.py tests? I'm sure I'm not the only person who wants to check the covered components, so this seems like it would be a very helpful demonstration.
The text was updated successfully, but these errors were encountered:
Would you consider an enhancement, maybe even a PR, so the verify method accepts an optional list of required component IDs, and declares failure if one is missing? Then I can ignore the double-quoted keys and simplify my code :) So instead of:
Thanks @kislyuk for getting back to me. I see I have combined many issues here :) The first is why the covered_components keys are double-double quoted-quoted, the second is asking for an example in the tests area, and the third is for a new behavior in the verify method. Please advise how to separate & handle.
I'm trying to check that the signature verify result includes certain fields, for example on a POST with a body, the content-digest should be covered. I discovered that the keys in the VerifyResult covered_components OrderedDict are quoted; i.e., start and end with double-quote characters. Is this essential? The values are not double-quoted so I am wondering if maybe this was an oversight. Please see example:
Just one more thing, would you please use the verify result in the
test.py
tests? I'm sure I'm not the only person who wants to check the covered components, so this seems like it would be a very helpful demonstration.The text was updated successfully, but these errors were encountered: