Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bug #52095 [Notifier][Sendinblue] Handle error responses without a me…
…ssage key (stof) This PR was merged into the 5.4 branch. Discussion ---------- [Notifier][Sendinblue] Handle error responses without a message key | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | | License | MIT During their outage yesterday where the endpoint returned errors with status code 500, there was no `message` key in the json response. This avoids a notice when the key does not exist. Instead, it uses the full response content, as done when the decoding fails. Commits ------- 8ae8993 Handle Sendinblue error responses without a message key
- Loading branch information