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

Save to JSON #39

Closed
Firesphere opened this issue Jul 16, 2019 · 1 comment
Closed

Save to JSON #39

Firesphere opened this issue Jul 16, 2019 · 1 comment

Comments

@Firesphere
Copy link
Contributor

Add the ability to save the generated headers to a JSON file.

Current situation

  • An engineer has to manually generate a JSON file or array to load the pre-set configuration
  • The updates to the configuration (e.g. user custom added domains) can not be saved in the JSON

Wished situation

  • Add an API point to export the generated CSP headers, minus calculated hashes, to a JSON or array
  • Enabling a much faster loading of the configuration (bypassing most of e.g. database calls)

Additional awesomeness

  • Make the loading and exporting time-based. If a change is detected compared to the latest version requested (e.g. latest change in a database), load and update the config afterwards

(I understand additional awesomeness is very project specific)

@paragonie-security
Copy link
Contributor

This is being done in #56 and will land in the next release.

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

No branches or pull requests

2 participants