Repository navigation
Retry Fever's catalogue page past a cached 500 - #943
Merged
Merged
Conversation
Fever serves its 500s with `cache-control: public, max-age=1800`, so CloudFront holds one for half an hour. A single 500 for catalogue page 2 voided a retrieve: the step retries replayed the cached listing page, rebuilt the identical URL and were handed the stored error each time. The tracker id is part of CloudFront's cache key but ignored by Fever, so retry a 500 on that endpoint with a fresh id each attempt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GBhsxTp8wmVmp88YNLNq44
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
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.
Fever serves its 500s with
cache-control: public, max-age=1800, soCloudFront holds one for half an hour. A single 500 for catalogue page 2
voided a retrieve: the step retries replayed the cached listing page,
rebuilt the identical URL and were handed the stored error each time.
The tracker id is part of CloudFront's cache key but ignored by Fever,
so retry a 500 on that endpoint with a fresh id each attempt.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01GBhsxTp8wmVmp88YNLNq44