Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
Commitf4b774f
committed
bug#52096 [Notifier] [Brevo] Handle error responses without a message key (stof)
This PR was merged into the 6.4 branch.Discussion----------[Notifier] [Brevo] Handle error responses without a message key| Q | A| ------------- | ---| Branch? | 6.4| Bug fix? | yes| New feature? | no| Deprecations? | no| Tickets || License | MITDuring 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.This is the same change than#52095 but for the new Brevo bridgeCommits-------517ceae Handle Brevo error responses without a message keyFile tree
2 files changed
+2
-2
lines changed- src/Symfony/Component
- Mailer/Bridge/Brevo/Transport
- Notifier/Bridge/Brevo
2 files changed
+2
-2
lines changedLines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
65 | 65 | | |
66 | 66 | | |
67 | 67 | | |
68 | | - | |
| 68 | + | |
69 | 69 | | |
70 | 70 | | |
71 | 71 | | |
| |||
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
75 | 75 | | |
76 | 76 | | |
77 | 77 | | |
78 | | - | |
| 78 | + | |
79 | 79 | | |
80 | 80 | | |
81 | 81 | | |
| |||
0 commit comments
Comments
(0)