Description
Validate each entity tag as an optionally uppercase W/-prefixed quoted token in the implemented byte range.
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.
Validate each entity tag as an optionally uppercase W/-prefixed quoted token in the implemented byte range.
When to use this tool
Use HTTP Etag Weak Strong Comparison Pair 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 first, second. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read weakEqual, strongEqual. Inspect weakEqual, strongEqual before interpreting the associated values.
Validate each entity tag as an optionally uppercase W/-prefixed quoted token in the implemented byte range. Remove only the weakness marker for weakEqual; strongEqual additionally requires both tags lack that marker.1
Weak entity-tag comparison ignores weakness markers; strong comparison additionally requires both validators to be strong.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| first | First | Required. Text; maximum UTF-16 length 8192. |
| second | Second | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| weakEqual | Weak Equal | Required. Boolean. |
| strongEqual | Strong Equal | Required. Boolean. |
{
"input": {
"first": "W/\"abc\"",
"second": "\"abc\""
},
"output": {
"weakEqual": true,
"strongEqual": false
}
}Limitations and assumptions
- Opaque tag contents remain case-sensitive. This compares two tags without parsing a header list or checking resource state, request method, preconditions, or representation identity.
- 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
- Cookie Samesite None Secure Pair
Check the supplied SameSite/Secure pair under the rule that SameSite None requires Secure.
- CSP Host Source Subdomain Wildcard Pair
Check only a lowercase ASCII host subdomain wildcard; scheme, port and path matching are outside this fragment.