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
Is your feature request related to a problem? Please describe.
In the current implementation of the trigger context, the body has already been parsed.
However several services make a signature of body based on rawBody request.
for example: "tax_formatted":"\u20ac0.57","discount_total":1199,"total_formatted":"\u20ac3.57",
will be decoded to json:
Is your feature request related to a problem? Please describe.
In the current implementation of the trigger context, the body has already been parsed.
However several services make a signature of body based on rawBody request.
for example: "tax_formatted":"\u20ac0.57","discount_total":1199,"total_formatted":"\u20ac3.57",
will be decoded to json:
"tax_formatted": "€0.57",
"discount_total": 1199,
"total_formatted": "€3.57",
as a result, it is impossible to restore the original rawBody.
In the end, the webhook signature is incorrect.
Describe the solution you'd like
context should have access to raw text body in case of json/urlencode-form request
Describe alternatives you've considered
as a workaround I switched off the trigger signaturecheck
Additional context
THe example of the system that uses such approach (signature against rawBody): https://docs.lemonsqueezy.com/help/webhooks
The text was updated successfully, but these errors were encountered: