fix: return 404 for unsupported filecoinpin ad sync status - #63
Merged
Conversation
Member
Author
|
This will not impede our progress; it is merely an optimization‑level fix. |
BigLep
approved these changes
Sep 9, 2026
github-project-automation
Bot
moved this from 🔎 Awaiting review
to ✔️ Approved by reviewer
in FOC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Requests to
/sync/status/ad/{adCid}currently fall through to a 307 redirect to the cid.contact root. Return404withCache-Control: no-storeso Curio skips this unsupported endpoint without attempting to decode the redirected response as JSON. Update the Worker's route documentation and retirement traffic checklist accordingly.