HTTP Method
An HTTP method is a word on a request that says what kind of action is intended. Each method has standard rules for safety, retries, and caching.
Another example
A document API uses `GET` to read without side effects and `PUT` to replace a known resource. It uses `PATCH` to edit part and `DELETE` to request removal. A link checker can safely send `HEAD`. A crawler must never approve an invoice through `GET`.
Main parts
- 01Method token
- 02Defined semantics
- 03Target resource
Use it when
Choose a registered method whose standard meaning fits the action. Document its conditions, data format, and reply.
Do not use it when
Do not change data with a safe method. Do not put every action behind `POST` when caches and other middle systems need standard meanings.
Name used in code
GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, PATCH Before you ship
Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback.
Outcome: Design or review HTTP Method for this system while keeping data correct, secure, and easy to operate. User context: A document API uses `GET` to read without side effects and `PUT` to replace a known resource. It uses `PATCH` to edit part and `DELETE` to request removal. A link checker can safely send `HEAD`. A crawler must never approve an invoice through `GET`. Technical concept or control: HTTP Method. Why it fits: Choose a registered method whose standard meaning fits the action. Document its conditions, data format, and reply. Do not use it when: Do not change data with a safe method. Do not put every action behind `POST` when caches and other middle systems need standard meanings. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.
Check this request
Review the current use of HTTP Method. Definition: An HTTP method is a word on a request that says what kind of action is intended. Each method has standard rules for safety, retries, and caching. Release checks: Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.