We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As Google is abandoning HPKP in favour of the Expect-CT header, we should implement that instead.
This makes things much easier, as it works like CSP but for Certificate Transparency. No more hashing certificates and updating a file.
Expect-CT: max-age=0, report-uri="https://scotthelme.report-uri.io/r/default/ct/reportOnly" Expect-CT: enforce,max-age=30,report-uri="https://scotthelme.report-uri.io/r/default/ct/enforce"
The text was updated successfully, but these errors were encountered:
This should probably be added to nginx-config/directive/bubbly_security-headers.conf
nginx-config/directive/bubbly_security-headers.conf
It would be good if this and CSP looked similar:
Sorry, something went wrong.
7883ebc
lewisgoddard
No branches or pull requests
As Google is abandoning HPKP in favour of the Expect-CT header, we should implement that instead.
This makes things much easier, as it works like CSP but for Certificate Transparency. No more hashing certificates and updating a file.
The text was updated successfully, but these errors were encountered: