Skip to content
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

feat(storage)!: Throw an error for 403 HTTP responses #212

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

manzt
Copy link
Owner

@manzt manzt commented Oct 1, 2024

FetchStore now throws an error for 403 (forbidden) responses. This is a breaking change because previously 404 and 403 responses were treated the same way. Now, only 404 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

Copy link

changeset-bot bot commented Oct 1, 2024

🦋 Changeset detected

Latest commit: c274017

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages
Name Type
@zarrita/storage Patch
@zarrita/core Patch
@zarrita/indexing Patch
@zarrita/ndarray Patch
zarrita Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@manzt manzt merged commit 361a7aa into main Oct 1, 2024
2 checks passed
@manzt manzt deleted the change-403-behavior branch October 1, 2024 20:17
@github-actions github-actions bot mentioned this pull request Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant