-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Cache-Control: private, no-store
headers where appropriate
#793
Labels
Comments
tashian
added
enhancement
needs triage
Waiting for discussion / prioritization by team
labels
Jan 10, 2022
km274
added a commit
to km274/certificates
that referenced
this issue
Jul 10, 2023
…s that respond with sensitive info. Fixes smallstep#793
km274
added a commit
to km274/certificates
that referenced
this issue
Jul 11, 2023
…s that respond with sensitive info. Fixes smallstep#793
km274
added a commit
to km274/certificates
that referenced
this issue
Jul 12, 2023
…s that respond with sensitive info. Fixes smallstep#793
km274
added a commit
to km274/certificates
that referenced
this issue
Jul 13, 2023
…s that respond with sensitive info. Fixes smallstep#793
km274
added a commit
to km274/certificates
that referenced
this issue
Jul 13, 2023
…s that respond with sensitive info. Fixes smallstep#793
km274
added a commit
to km274/certificates
that referenced
this issue
Jul 20, 2023
…s that respond with sensitive info. Fixes smallstep#793
km274
added a commit
to km274/certificates
that referenced
this issue
Sep 15, 2023
…s that respond with sensitive info. Fixes smallstep#793
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The recommendation is to set
Cache-Control: private, no-store
on any endpoint with sensitive information. Because while you can protect the traffic with TLS, you also need to keep sensitive information out of a client's (unencrypted) HTTP cache. I'm not sure how relevant this is to the API context ofstep-ca
though—I've never seen an HTTP client library that caches content. But I guess the point here is that a client could cache any content unless we tell it not to.The text was updated successfully, but these errors were encountered: