-
Notifications
You must be signed in to change notification settings - Fork 449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(hosted-hpb): Correctly handle API response when the account expir… #10970
fix(hosted-hpb): Correctly handle API response when the account expir… #10970
Conversation
// Account was deleted, so remove the information locally | ||
$accountInfo = ['status' => 'deleted']; | ||
} elseif ($e->getCode() === Http::STATUS_UNAUTHORIZED) { | ||
// Account is expired and deletion is pending unless it's reactivated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it seems previously expired accounts always received a 200 with body. Now it's a 401. Deleted accounts receive a 404.
So both cases are now specifically catched and handled so the status notifications happen as planned.
…ed or was deleted Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
5bae204
to
f40fc78
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All that is close to my level of understanding, seems OK
Signed-off-by: Joas Schilling <coding@schilljs.com>
/backport to stable27 |
/backport to stable26 |
…ed or was deleted
☑️ Resolves
🛠️ API Checklist
🏁 Checklist
docs/
has been updated or is not required