Description
Lowercase headerName and return recognized for content-security-policy or content-security-policy-report-only.
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.
Lowercase headerName and return recognized for content-security-policy or content-security-policy-report-only.
When to use this tool
Use Content Security Policy Report Only Label 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 headerName. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read reportOnly, recognized. Inspect reportOnly, recognized before interpreting the associated values.
Lowercase headerName and return recognized for content-security-policy or content-security-policy-report-only. Set reportOnly only for the latter.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| headerName | Header Name | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| reportOnly | Report Only | Required. Boolean. |
| recognized | Recognized | Required. Boolean. |
{
"input": {
"headerName": "Content-Security-Policy-Report-Only"
},
"output": {
"reportOnly": true,
"recognized": true
}
}Limitations and assumptions
- Whitespace is not trimmed and the field value is not inspected. The label does not validate a policy, model violations, or prove any browser enforcement behavior.
- 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
- Content Disposition RFC 5987 Language Field
Split value around the first two apostrophe-delimited fields into charset, language, and encodedValue, requiring a nonempty whitespace-free charset and no carriage return or newline.
- Cookie Host Only Domain Attribute Flag
Treat empty domainAttribute as hostOnly.