Skip to content

fix: disable caching for authentication and secret responses - #25

Merged
MugdhoAI merged 5 commits into
mainfrom
fix/no-store-sensitive-responses
Oct 24, 2026
Merged

MugdhoAI merged 5 commits into
mainfrom
fix/no-store-sensitive-responses

Conversation

@MugdhoAI

Copy link
Copy Markdown
Owner

Summary

  • Add Cache-Control: no-store to authentication and secret-management responses, including error responses.
  • Add regression assertions for registration/login and secret create/list/read/update/delete responses.
  • Document the response caching policy in the README.

Why

The API returns access tokens and decrypted secret values. Explicitly preventing cache storage reduces the chance that clients or intermediaries retain sensitive responses.

Verification

  • GitHub Actions will run dependency audit, Ruff, Docker and Compose validation, PostgreSQL-backed tests on Python 3.12–3.14, and CodeQL.

@MugdhoAI
MugdhoAI merged commit cf71691 into main Oct 24, 2026
5 checks passed
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.

1 participant