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

gateway: add 429 handling and ErrGatewayRetryAfter #188

Closed
1 of 2 tasks
lidel opened this issue Feb 27, 2023 · 0 comments · Fixed by #194
Closed
1 of 2 tasks

gateway: add 429 handling and ErrGatewayRetryAfter #188

lidel opened this issue Feb 27, 2023 · 0 comments · Fixed by #194
Assignees
Labels
need/triage Needs initial labeling and prioritization topic/gateway Issues related to HTTP Gateway

Comments

@lidel
Copy link
Member

lidel commented Feb 27, 2023

We need a mechanism for signaling to the client when gateway has a cached failure, and when it is ok to retry.
The initial use will be filecoin-saturn/caboose#44 but this will be useful beyond that – in the future, gateway operators will be able to write custom throttling logic, and this error will take care of HTTP semantics.

I propose we:

@lidel lidel added the need/triage Needs initial labeling and prioritization label Feb 27, 2023
@hacdias hacdias self-assigned this Feb 28, 2023
@hacdias hacdias moved this to 🥞 Todo in IPFS Shipyard Team Feb 28, 2023
@hacdias hacdias moved this from 🥞 Todo to 🏃‍♀️ In Progress in IPFS Shipyard Team Mar 3, 2023
@hacdias hacdias moved this from 🏃‍♀️ In Progress to 🔎 In Review in IPFS Shipyard Team Mar 3, 2023
@lidel lidel added the topic/gateway Issues related to HTTP Gateway label Mar 3, 2023
@github-project-automation github-project-automation bot moved this from 🔎 In Review to 🎉 Done in IPFS Shipyard Team Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization topic/gateway Issues related to HTTP Gateway
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants