feat(storage)!: Throw an error for 403 HTTP responses #212
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FetchStore
now throws an error for 403 (forbidden) responses. This is a breaking change because previously404
and403
responses were treated the same way. Now, only404
responses signify a "missing" key from the store.I believe this carries the correct semantics around 404 and 403 responses. If you disagree, please let me know and we can discuss how to extend the
FetchStore
to be more flexible with handling responses.see: hms-dbmi/vizarr#214