You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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? :)
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.
The CSP spec has a nice requirement that CSP reports should have the
content-type
header set toapplication/csp-report
. https://www.w3.org/TR/CSP2/#send-violation-reportsCould we introduce a similar requirement for HPKP reports to have a
content-type
header set toapplication/hpkp-report
?The text was updated successfully, but these errors were encountered: