The HTTP Sec-Private-State-Token-Crypto-Version Fetch Metadata Request Header is used by the Private State Token API during token issuance to indicate to the issuer server which cryptographic protocol version should be used to sign blinded nonces when generating tokens.
At the time of writing, there is only one version supported, but this mechanism makes it possible to support multiple versions in the future.
Note that a developer wouldn't be expected to generate Sec-Private-State-Token-Crypto-Version request headers — these are created automatically by the browser when invoking private state token token-request fetch requests.
<table class="properties"> <tbody> <tr> <th scope="row">Header type</th> <td>Fetch Metadata Request Header</td> </tr> <tr> <th scope="row">Forbidden request header</th> <td>Yes (<code>Sec-</code> prefix)</td> </tr> <tr> <th scope="row"> CORS-safelisted request header </th> <td>No</td> </tr> </tbody> </table>
Syntax
Sec-Private-State-Token-Crypto-Version: <string>
Servers should ignore this header if it contains any other value.
Directives
<string>- : A string containing the cryptographic protocol version that should be used by the issuer server to sign blinded nonces when generating tokens.
Examples
Sec-Private-State-Token-Crypto-Version: PrivateStateTokenV1VOPRF
Specifications
Browser compatibility
See also
- Sec-Private-State-Token
- Sec-Private-State-Token-Lifetime
- Sec-Redemption-Record
- Private State Token API
来源:MDN Web Docs / Mozilla 贡献者 · 作者与贡献记录 · CC BY-SA 2.5。离线整理了版式、链接和媒体显示。
