[FIX] webhook-timestamp
header to use current seconds since epoch value instead of event timestamp
#5521
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Using the same timestamp value in the payload and in the
webhook-timestamp
(this one used for verification) was causing an "message too old" error when verifying the webhook message.Replacing it to be calculated in the moment of the webhook request should solve these associated problems.
Type of change
How Has This Been Tested
Checklist