Description
Treat empty domainAttribute as hostOnly.
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.
Treat empty domainAttribute as hostOnly.
When to use this tool
Use Cookie Host Only Domain Attribute Flag 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 domainAttribute. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read hostOnly, normalizedDomain. Inspect hostOnly before interpreting the associated values.
Treat empty domainAttribute as hostOnly. Otherwise validate the implemented ASCII domain-like subset, remove one optional leading dot, lowercase it, and return normalizedDomain.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| domainAttribute | Domain Attribute | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| hostOnly | Host Only | Required. Boolean. |
| normalizedDomain | Normalized Domain | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"domainAttribute": ".Example.com"
},
"output": {
"hostOnly": false,
"normalizedDomain": "example.com"
}
}Limitations and assumptions
- This does not bind an empty attribute to a request host or validate public suffixes, label lengths, IDNA, or domain acceptance. The lexical subset can admit labels unsuitable for actual DNS use.
- 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
- Cookie Domain Leading Dot Normalization
Remove one optional leading dot and require a hostname no longer than 253 characters with ASCII labels from one through 63 characters and no leading or trailing hyphen.
- Content Security Policy Report Only Label
Lowercase headerName and return recognized for content-security-policy or content-security-policy-report-only.