Description
Return valid when method is a nonempty sequence of the implemented HTTP token characters.
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.
Return valid when method is a nonempty sequence of the implemented HTTP token characters.
When to use this tool
Use HTTP Allow Header Single Method Token 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 method. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid. Inspect valid before interpreting the associated values.
Return valid when method is a nonempty sequence of the implemented HTTP token characters.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| method | Method | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| valid | Whether this tool’s particular check passes; does not imply broader identifier or protocol validity. | Required. Boolean. |
{
"input": {
"method": "PATCH"
},
"output": {
"valid": true
}
}Limitations and assumptions
- This checks one lexical method token, including extension spellings. It does not consult the method registry, parse a comma-separated Allow field, or determine server support.
- 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 Method Case Sensitivity Tag
Validate left and right as method-token spellings, compare them exactly for sameMethod, and separately flag differsOnlyByCase when unequal spellings become equal after lowercasing.
- HTTP Vary Header Star Dominance
Validate each fields entry as a field-name token or star.