In our backends we have set a limit for the size of incoming json payload up to 10mb, but we don't log any useful info when the request is too large and gets rejected.
So we're not able to investigate who's sending those requests and eventually spot a bug on our side.
Details
No response
Version
2.8.0
Steps to reproduce
There's no easy was to reproduce this at the moment, but at high level these should be the steps:
generate a json bigger than 10MB
generate a keypair for signing the request payload
sign the payload and use the signature in X-YTtrex-Signature header
Description
In our backends we have set a limit for the size of incoming
json
payload up to 10mb, but we don't log any useful info when the request is too large and gets rejected. So we're not able to investigate who's sending those requests and eventually spot a bug on our side.Details
No response
Version
2.8.0
Steps to reproduce
There's no easy was to reproduce this at the moment, but at high level these should be the steps:
X-YTtrex-Signature
headerX-YTtrex-PublicKey
headerPOST /v1/events
Code example, screenshot, or link to a repository
No response