medium10 pts · first answer countscachinghttpsecurity

CDN serves one user's profile to another

After putting a CDN in front of your API, user B sometimes receives user A's data from GET /me. Which response header change fixes this?

A.Send Cache-Control: private (or no-store) on per-user responses so shared caches do not store themB.Send Cache-Control: public, max-age=3600C.Add an ETag header so the CDN revalidates every response with the origin before serving it to any userD.Switch the CDN to HTTP/3

← Keeping a cached price fresh Take the medium mock interview →