Description
Reject carriage returns, newlines, and commas in metadata.
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 carriage returns, newlines, and commas in metadata.
When to use this tool
Use Data URI Default Media Type 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 metadata. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read mediaType, defaulted. Inspect defaulted before interpreting the associated values.
Reject carriage returns, newlines, and commas in metadata. Inspect the first semicolon-separated component: if empty return mediaType text/plain with defaulted true; otherwise validate the implemented type/subtype token subset and lowercase it.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| metadata | Metadata | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| mediaType | Media Type | Required. Text; maximum UTF-16 length 8192. |
| defaulted | Defaulted | Required. Boolean. |
{
"input": {
"metadata": ";base64"
},
"output": {
"mediaType": "text/plain",
"defaulted": true
}
}Limitations and assumptions
- Metadata is the portion before a data URI's comma, without the data: prefix. Later parameters and payload are not validated, and no default charset or base64 decoding is performed.
- 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
- Data URI Base64 Marker Position
Reject commas in metadata, split on semicolons, and locate components equal to base64 ignoring case.
- Link Relation Extension URI Label
Reject empty relation or any whitespace.