Description
Return weak and the literal opaque value.
HTTP fields use specific token, quoted-string, range, quality-weight, and entity-tag grammars. Quoted text is not automatically safe as a filename or equivalent to an escaped string in another language. Parsing one parameter or marker is separate from interpreting a full request or response.
Return weak and the literal opaque value.
When to use this tool
Use HTTP Etag Weak Prefix Token when you need to parse this one supported HTTP field component or parameter token.
How to use the tool and how it works
- Enter token. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read weak, opaque. Inspect weak before interpreting the associated values.
Accept an optional uppercase W/ prefix and a double-quoted opaque value composed of permitted visible/Latin-1-range characters. Return weak and the literal opaque value.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Complete literal token in the grammar stated above. | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| weak | Whether uppercase W/ was present. | Required. Boolean. |
| opaque | Literal opaque-tag content; backslashes are not unescaped. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"token": "W/\"abc\""
},
"output": {
"weak": true,
"opaque": "abc"
}
}Limitations and assumptions
- The weak prefix is case-sensitive and backslash is an ordinary opaque character rather than an escape. No resource comparison, cache validation, unquoting beyond the wrapper, or HTTP request is performed.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use a full header parser and the relevant HTTP semantics when request behavior depends on the result. Check extended parameters, field context, and downstream use of returned text separately.
References
Similar or alternative tools
- HTTP Range Single Suffix Token
Return length as a nonnegative safe integer and nonzero when length>0.
- Parsing: HTTP Qvalue Single Token
Parse one strict RFC9110 qvalue, allowing at most three fractional digits and only zero fractions after one; no whole-header parsing.