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.

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

Possible New 404 and 429 Public Frontend Approach #530

Open
michaelquigley opened this issue Jan 12, 2024 · 0 comments
Open

Possible New 404 and 429 Public Frontend Approach #530

michaelquigley opened this issue Jan 12, 2024 · 0 comments
Assignees
@michaelquigley
Labels
enhancement Enhancement of an existing feature
Milestone
v0.5

Comments

@michaelquigley
Copy link
Collaborator

If we end up with some kind of "cache advice" framework (as a result of correcting #529), we might be able to start re-wiring released and over-quota shares such that the frontend can just return a 404 or a 429 based on the wired configuration of the underlying share.
@michaelquigley michaelquigley self-assigned this Jan 12, 2024
@michaelquigley michaelquigley added the enhancement Enhancement of an existing feature label Jan 12, 2024
@michaelquigley michaelquigley added this to the v0.5 milestone Jan 12, 2024
@michaelquigley michaelquigley changed the title Possible New 404 and 492 Public Frontend Approach Possible New 404 and 429 Public Frontend Approach Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelquigley michaelquigley

Labels
enhancement Enhancement of an existing feature
Projects
zrok Development Roadmap
Status: Backlog
Milestone
v0.5
Development

No branches or pull requests
1 participant
@michaelquigley