Description
Reject commas in metadata, split on semicolons, and locate components equal to base64 ignoring case.
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 commas in metadata, split on semicolons, and locate components equal to base64 ignoring case.
When to use this tool
Use Data URI Base64 Marker Position 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 base64, validPosition. Inspect base64, validPosition before interpreting the associated values.
Reject commas in metadata, split on semicolons, and locate components equal to base64 ignoring case. Return base64 when any are present; validPosition requires none, or exactly one final marker after at least one earlier component.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| metadata | Metadata | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| base64 | Base64 | Required. Boolean. |
| validPosition | Valid Position | Required. Boolean. |
{
"input": {
"metadata": "text/plain;base64;charset=utf-8"
},
"output": {
"base64": true,
"validPosition": false
}
}Limitations and assumptions
- A bare base64 component is therefore present but in an invalid position. This does not validate media types, parameters, base64 content, or data URI syntax as a whole.
- 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 Default Media Type Token
Reject carriage returns, newlines, and commas in metadata.
- URI Query Empty Value Equals Marker
Split token at its first equals sign into name and value, returning hasEquals.