fix: sitemap aggregate timeout + CDN caching - #2090
Merged
Merged
Conversation
- /fee-compare/[venueA]/[venueB]/[wallet] dynamic route auto-submits on load - pushState updates URL after analyze so any comparison is shareable - FeeCompareClient accepts initialVenueA/B/Wallet/Days props - HL wallet side: replace 2-cell grid with inline fee/funding/net breakdown
Flotapponnier
added a commit
that referenced
this pull request
Aug 26, 2026
* feat: shareable wallet URLs + HL fee/funding breakdown - /fee-compare/[venueA]/[venueB]/[wallet] dynamic route auto-submits on load - pushState updates URL after analyze so any comparison is shareable - FeeCompareClient accepts initialVenueA/B/Wallet/Days props - HL wallet side: replace 2-cell grid with inline fee/funding/net breakdown * fix: remove 'No activity found' text from crossSim projection side * fix: sitemap aggregate timeout + CDN caching (s-maxage stripped by dynamic route)
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
1 participant
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.
Summary
/api/aggregateroute hadcache: \"no-store\"on its internal fetch, which caused Next.js to treat the route as dynamic and strips-maxagefrom the response header — so Vercel CDN always returnedx-vercel-cache: MISS, fetching 7.6 MB from the Paris VPS on every requestFETCH_TIMEOUT_MSinaggregate-blob.tswas 20 s, but the Paris VPS takes 37–49 s uncompressed (18 s compressed). The aggregate blob fetch always timed out →loadAggregateFromBlob()always returned null → sitemap fell back to 192-URL static fallback → Google Search Console dropped from 650 to 18 indexed pages around Aug 8Changes
api/aggregate/route.ts: removecache: \"no-store\"(lets Next.js keeps-maxage=60in the response → Vercel CDN can cache it), addexport const revalidate = 60for ISR-style caching, raiseUPSTREAM_TIMEOUT_MS25 s → 70 saggregate-blob.ts: raiseFETCH_TIMEOUT_MS20 s → 65 s (above measured VPS response time)sitemap-builder.ts: raise sitemap build timeout 45 s → 120 sExpected result
After one cold-cache request (first hit after deployment, ~18 s compressed),
/api/aggregateis ISR-cached for 60 s. All subsequent sitemap builds within that window use cached data and complete in < 10 s, returning 750+ URLs instead of 192.Test plan
curl -sI https://<preview>/api/aggregate | grep cache— should shows-maxage=60x-vercel-cache: HITon second request to/api/aggregatecurl -s https://<preview>/sitemap.xml | grep -o '<url>' | wc -lreturns 750+