Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Is setting the cache-control header to no-cache for the server necessary? #7

Open
H0R5E opened this issue Sep 9, 2024 · 0 comments
Open

Is setting the cache-control header to no-cache for the server necessary? #7

H0R5E opened this issue Sep 9, 2024 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@H0R5E
Copy link
Member

H0R5E commented Sep 9, 2024

A legacy feature from sveltekit-adapter-aws is that the cache-control header is set to no-cache for all server responses. See, for example, here.

The logic behind this is not explained, and it might be that caching the server responses is OK. Needs futher investigation.
@H0R5E H0R5E added the help wanted Extra attention is needed label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@H0R5E