high75%
Link header values accumulate after Cache Components revalidation when next/font is used with middleware proxy
When a Next.js application uses Cache Components with time-based revalidation, a middleware proxy that sets a Link header (e.g., alternate hreflang links) and next/font/local font preloads, each revalidation appends a new set of Link headers instead of replacing the previous set, causing unbounded header growth and eventual 502 errors.