Description
Check literal cookie path matching using equality and slash-boundary prefix rules.
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.
Check literal cookie path matching using equality and slash-boundary prefix rules.
When to use this tool
Use Cookie Path Prefix Boundary Flag 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 cookiePath, requestPath. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read matches. Inspect matches before interpreting the associated values.
Require cookiePath and requestPath to start with slash. Match exact equality, or a request prefix when the cookie path ends with slash or the next request character is slash.1
Cookie path matching uses equality or a path prefix with the required slash boundary.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| cookiePath | Cookie Path | Required. Text; maximum UTF-16 length 8192. |
| requestPath | Request Path | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| matches | Whether the supplied values match under the particular stated rule. | Required. Boolean. |
{
"input": {
"cookiePath": "/foo",
"requestPath": "/foobar"
},
"output": {
"matches": false
}
}Limitations and assumptions
- The boundary rule prevents /a from matching /ab. This compares supplied path strings without URL decoding, domain checks, cookie expiry, or browser storage selection.
- 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
- HTTP Cookie Duplicate Path Tie Token
Order eligible same-name cookies by longer supplied path then earlier creation; request applicability is supplied, not inferred.
- Cache Directive Delta Seconds Boundary
Return a delta-seconds token's exact decimal value and a numeric interpretation capped at 2147483648.