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.

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

Edited Cache Control (CRASM-667) #700

Merged
merged 1 commit into from
Oct 24, 2024
Merged

Conversation

hawkishpolicy
Copy link
Collaborator

Edited both browser and http cache control to prevent cache and store and also force revalidate.

🗣 Description

  • HTTP cache control header is set to no-cache, no-store, must-revalidate.
  • Browser cache is set to no-cache, no-store, must-revalidate.

💭 Motivation and context

🧪 Testing

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • Changes are limited to a single goal - eschew scope creep!
  • All future TODOs are captured in issues, which are referenced
    in code comments.
  • All relevant type-of-change labels have been added.
  • I have read the CONTRIBUTING document.
  • These code changes follow cisagov code standards.
  • All new and existing tests pass.

✅ Pre-merge checklist

  • Revert dependencies to default branches.
  • Finalize version.

✅ Post-merge checklist

  • Create a release.

- HTTP cache control header is set to no-cache, no-store, must-revalidate.
Browser cache is set to no-cache, no-store, must-revalidate.
@schmelz21 schmelz21 merged commit 98306bc into develop Oct 24, 2024
11 of 14 checks passed
@schmelz21 schmelz21 deleted the Set-http-no-cach-CRASM-667 branch October 24, 2024 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants