Finding: Cacheable HTTPS

> Applications should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:

> `Cache-control: no-store`
> `Pragma: no-cache`

Update headers to remediate this finding.

Locate the web server or application response configuration that controls headers for sensitive content, then review how relevant responses are identified. Confirm completion by verifying those responses include Cache-control: no-store and Pragma: no-cache, using the project’s available checks or by inspecting response headers.

Written by the indexing model from the issue text.