Skip to content
This repository has been archived by the owner on Mar 8, 2024. It is now read-only.

Cache-Control Header max-age=0 is Implicit in no-store #23

Closed
jscottbranson opened this issue Jun 22, 2020 · 2 comments
Closed

Cache-Control Header max-age=0 is Implicit in no-store #23

jscottbranson opened this issue Jun 22, 2020 · 2 comments

Comments

@jscottbranson
Copy link

The rfcs require the 'Cache-Control' response header be set to 'max-age=0', however, it appears to be more appropriate to use the 'no-store' directive, as it is more broad in that it assumes 'max-age=0' as well as 'must-revalidate'.

Credit to @RareData for talking through which headers are appropriate with me. Markus also observed that the 'no-transform' directive might be appropriate.

Also credit to @XRPL-Labs, whose PayID implementation first alerted me to the 'no-store' directive.

@aanchal4
Copy link
Collaborator

Thanks @CrypticRabbit for bringing this up. Sounds reasonable to me! Will update the RFC in next iteration.

@jscottbranson
Copy link
Author

Just circling back to this, thanks for merging.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants