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

Handle Expect-CT and Expect-Staple violation reports #5133

Closed
graingert opened this issue Mar 22, 2017 · 3 comments · Fixed by #8213
Closed

Handle Expect-CT and Expect-Staple violation reports #5133

graingert opened this issue Mar 22, 2017 · 3 comments · Fixed by #8213
Assignees

Comments

@graingert
Copy link
Contributor

To expand upon the CSP reporting support added in #729 and #2154, would love to have Expect-CT and Expect-Staple reporting support as well. This would really make Sentry very useful for handling these reports coming from browsers.

See also #2165 and https://report-uri.io/

@reedloden
Copy link
Contributor

Coinbase just blogged about the usefulness of this header -- https://engineering.coinbase.com/moving-to-expect-ct-d0d26a07046d

@alex-hofsteede
Copy link
Contributor

#6417 Currently adds both HPKP and Expect-CT error report ingestion, but given the imminent deprecation of HPKP in Chrome, I think we may ship it with just Expect-CT

@reedloden
Copy link
Contributor

This is done in #6417! woot.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants