Description
Split a strict ASCII RFC9110 entity tag into weak marker and opaque payload; backslash is an ordinary opaque character, not a quoted-string escape.
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.
Split a strict ASCII RFC9110 entity tag into weak marker and opaque payload; backslash is an ordinary opaque character, not a quoted-string escape.
When to use this tool
Use Web: Etag Weakness Marker Split 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 etag. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Require an optional uppercase W/ marker followed by a quoted ASCII opaque tag in the implemented character subset. Return weak and the unquoted opaqueTag inside result.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| etag | Etag | Required. Text. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Result | Required. Object. |
{
"input": {
"etag": "W/\"abc\""
},
"output": {
"result": {
"weak": true,
"opaqueTag": "abc"
}
}
}Limitations and assumptions
- The marker and tag are case-sensitive and this subset excludes non-ASCII bytes. No entity-tag list, escaping convention, conditional request, or resource comparison is evaluated.
- Outputs are nested inside result. 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.
- HTTP Etag Weak Strong Comparison Pair
Validate each entity tag as an optionally uppercase W/-prefixed quoted token in the implemented byte range.