Description
Validate left and right as method-token spellings, compare them exactly for sameMethod, and separately flag differsOnlyByCase when unequal spellings become equal after lowercasing.
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 left and right as method-token spellings, compare them exactly for sameMethod, and separately flag differsOnlyByCase when unequal spellings become equal after lowercasing.
When to use this tool
Use HTTP Method Case Sensitivity Tag 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 left, right. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read sameMethod, differsOnlyByCase. Inspect sameMethod, differsOnlyByCase before interpreting the associated values.
Validate left and right as method-token spellings, compare them exactly for sameMethod, and separately flag differsOnlyByCase when unequal spellings become equal after lowercasing.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| left | Left | Required. Text; maximum UTF-16 length 8192. |
| right | Right | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| sameMethod | Same Method | Required. Boolean. |
| differsOnlyByCase | Differs Only By Case | Required. Boolean. |
{
"input": {
"left": "GET",
"right": "get"
},
"output": {
"sameMethod": false,
"differsOnlyByCase": true
}
}Limitations and assumptions
- Method identity remains case-sensitive and accepted syntax does not establish a registered or supported method. This does not parse a request or contact a server.
- 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 Allow Header Single Method Token
Return valid when method is a nonempty sequence of the implemented HTTP token characters.
- HTTP Age Cache Freshness Residual
Calculate remaining cache freshness lifetime and mark exact lifetime equality as no longer fresh.