Description
Reject empty relation or any whitespace.
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.
Reject empty relation or any whitespace.
When to use this tool
Use Link Relation Extension URI 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 relation. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read kind, normalized. Use the output convention below.
Reject empty relation or any whitespace. If it starts with an ASCII URI-scheme prefix, classify it as extension-uri and preserve it; otherwise require the implemented letter-led token syntax, lowercase it, and label it registered-token.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| relation | Relation | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| kind | Lexical label registered-token or extension-uri, without registry verification. | Required. Text; maximum UTF-16 length 8192. |
| normalized | Normalized | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"relation": "https://example.com/relation"
},
"output": {
"kind": "extension-uri",
"normalized": "https://example.com/relation"
}
}Limitations and assumptions
- Registered-token is a lexical classification, not an IANA registry lookup. A recognized scheme prefix does not validate the remaining URI, resolve a link, or establish a known relation.
- 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 Security Policy Report Only Label
Lowercase headerName and return recognized for content-security-policy or content-security-policy-report-only.
- Data URI Base64 Marker Position
Reject commas in metadata, split on semicolons, and locate components equal to base64 ignoring case.