HTTP Methods

Updated 17 Sep 2026

•
What it is
- •
  request methods express the intended operation on a resource
•
Safe
- •
  the requested semantics are essentially read-only
- •
  GET, HEAD, OPTIONS, and TRACE are defined as safe
- •
  incidental effects such as request logging can still occur
•
Idempotent
- •
  repeating the same request has the same intended server effect as performing it once
- •
  safe methods, PUT, and DELETE are idempotent by definition
- •
  POST and PATCH are not guaranteed to be idempotent
•
Example
- •
  repeating a PUT that sets a field to "Budi" keeps that intended value
- •
  a repeated DELETE may return a different status while retaining the same intended final state
•
Caution
- •
  safe does not mean “secure,” and idempotent does not mean “identical response”
•
Source
- •
  https://www.rfc-editor.org/rfc/rfc9110.html#section-9.2

Linked references 2