docs: improve signed webhook event payload encoding #1102
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.
If the payload contains slashed and if you encode the data manually, then the default
json_encode
function escapes the slashes which causes the verification to fail.In my case, I decoded the payload with
json_decode
and then encoded it before the verification. However, the payload contained the user agent data, which has slashes, and thejson_encode
function was escaping the slashes, causing the verification to fail. So, I encoded the data likejson_encode($payload, JSON_UNESCAPED_SLASHES)
with the flag, and it started to verify successfully.