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

HPKP: Set Content-Type header field in reports #526

Open
ScottHelme opened this issue Jan 30, 2017 · 4 comments
Open

HPKP: Set Content-Type header field in reports #526

ScottHelme opened this issue Jan 30, 2017 · 4 comments

Comments

@ScottHelme
Copy link

The CSP spec has a nice requirement that CSP reports should have the content-type header set to application/csp-report. https://www.w3.org/TR/CSP2/#send-violation-reports

Could we introduce a similar requirement for HPKP reports to have a content-type header set to application/hpkp-report?

@mikewest
Copy link
Member

mikewest commented Feb 2, 2017

We could not, as HPKP is defined in the IETF. Also the websec group is closed. Soooo... @mnot, what's the process for asking for changes? File errata? :)

@annevk
Copy link
Member

annevk commented Feb 2, 2017

Oh great, these violation reports violate the same-origin policy. Whee.

@mnot
Copy link
Member

mnot commented Feb 2, 2017

Officially, errata aren't for technical changes/updates. You'd need a new RFC that updates or obsoletes the HPKP RFC.

Easiest way to do that would be to ask for the HTTP WG to take it on; we'd keep the source in our repo so that future updates would be easier.

All that said, in the meantime you can file errata that ask for technical changes -- they'll be listed as "Hold for Document Update", so at least they'll be somewhere.

@mnot
Copy link
Member

mnot commented Feb 2, 2017

And by "ask", I mean "provide an editor" :)

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

4 participants