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.

Sign up for GitHub

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

Jump to bottom

specs: clarify blob "not available" error types and HTTP status codes for different scenarios #355

Open

bnewbold opened this issue Oct 17, 2024 · 0 comments

Labels

specs

Contributor

bnewbold commented Oct 17, 2024

For example, what is the expected HTTP status code and error type for these scenarios:

blob did exist, but has been deleted (probably just 404?)
blob is associated with an account which is suspended
... same but for deleted account
... same but for deactivated account
... same but for permanently takendown account
blob has been purged as an infrastructure takedown action
blob should be returned, but there was data corruption / data loss and can't be
blob is referenced by a record, but it was lost during an account migration
account has used too much bandwidth quota (?)

bnewbold added the specs label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment