Next.js · Senior · Question 71 of 75
A CDN in front of a self-hosted Next.js keeps serving an old page after revalidateTag(). Why?
- ✓Correct answer: Revalidation clears only the Next.js server cache; the CDN keeps its copy until
s-maxageexpires unless you purge it - 2
revalidateTagdoesn't work when self-hosting - 3CDNs ignore
Cache-Control
Explanation
ISR pages are sent with s-maxage and stale-while-revalidate. Call the CDN purge API for both HTML and RSC variants alongside revalidation.