Description
Parse a single-quoted token containing exactly sha256, sha384, or sha512 followed by a hyphen and a base64-like digest.
Web protocol data has several layers: a complete message or URL, individual fields or components, and the literal tokens within them. Delimiter presence, spelling, comparison rules, and parser normalization can affect results. A check of one component needs its stated scope before it can be used in a larger parser or policy decision.
Parse a single-quoted token containing exactly sha256, sha384, or sha512 followed by a hyphen and a base64-like digest.
When to use this tool
Use Csp Hash Source Algorithm Token when you need one stated URL, header, or protocol-component check in a diagnostic or parser workflow. Supply the input level specified below.
How to use the tool and how it works
- Enter token. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read algorithm, digest. Use the output convention below.
Parse a single-quoted token containing exactly sha256, sha384, or sha512 followed by a hyphen and a base64-like digest. Return algorithm and digest without the surrounding source syntax.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| algorithm | Algorithm | Required. Text; maximum UTF-16 length 8192. |
| digest | Base64-like digest spelling, without decoded-length or content-hash verification. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"token": "'sha256-YWJj'"
},
"output": {
"algorithm": "sha256",
"digest": "YWJj"
}
}Limitations and assumptions
- The digest is screened for allowed characters and up to two trailing equals signs, not decoded or checked for algorithm-specific byte length. No content is hashed and no CSP permission is established.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
Alternative or Complementary methods
Use a complete URL or header parser when the task involves an entire field or message. Test actual browser, server, or cache behavior separately when a security or protocol decision depends on more than this component.
References
Similar or alternative tools
- CSP Host Source Subdomain Wildcard Pair
Check only a lowercase ASCII host subdomain wildcard; scheme, port and path matching are outside this fragment.
- Csp Wildcard Port Source Token
Parse source as a host-like token followed by colon and either star or one through five digits.