Skip to content

Conversation

@papey
Copy link
Member

@papey papey commented Jan 30, 2025

Context

We don't want any cache mechanism on requests that contains sensitive data

Changes

Added cache header instruction no-store, see related MDN documentation

@papey papey self-assigned this Jan 30, 2025
@papey papey requested a review from gcxRun as a code owner January 30, 2025 15:24
@papey papey changed the title replace-cache-header-instruction-with-no-store: Change cache header instruction add-no-store-instruction-header: Add no store instruction for cache header Feb 3, 2025
@papey papey force-pushed the replace-cache-header-instruction-with-no-store branch from 2d3d99f to 19db94c Compare February 3, 2025 15:25
assert_headers(headers, [
{"access-control-allow-origin", "*"},
{"cache-control", "no-cache"},
{"cache-control", "no-cache, no-store"},
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shall we do exactly as siiloSSE?

Suggested change
{"cache-control", "no-cache, no-store"},
{"cache-control", "no-cache, no-store, max-age=0, must-revalidate"},

Copy link
Contributor

@achouippe achouippe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's first try by adding no-store only.

@papey papey merged commit c121848 into main Feb 7, 2025
5 checks passed
@papey papey deleted the replace-cache-header-instruction-with-no-store branch February 7, 2025 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants