Cacheability is a REST constraint: a response must indicate whether its data may be reused for a later, equivalent request. HTTP response headers carry that decision. Clear caching rules can reduce client work and improve API performance without accidentally serving stale data. section 8.2 section 1.1.4
For a board-game API built with ASP.NET Core, the [ResponseCache] attribute sets Cache-Control directives on controller responses:
- Mark a GET response cacheable with [ResponseCache(Location = ResponseCacheLocation.Any, Duration = 60)]. section 8.2
- Prevent storage of a response with [ResponseCache(NoStore = true)]. section 8.2
Apply the appropriate setting to each response, then check its Cache-Control header. Clients and intermediate proxies use these directives to decide whether they may reuse the response. The practical choice is not simply whether caching is faster, but whether reuse is safe for that response. section 8.2 section 1.1.4

