ZeroServer.tools

HTTP Methods Reference

Quick reference for all 9 HTTP methods — safe, idempotent, cacheable, body rules, and status codes.

Method	Safe	Idempotent	Body	Cacheable	RFC	Summary
GET	Yes	Yes	No	Yes	RFC 9110	Retrieve a representation of the target resource.
POST	No	No	Yes	No	RFC 9110	Submit data to be processed by the target resource.
PUT	No	Yes	Yes	No	RFC 9110	Replace the target resource with the request payload.
PATCH	No	No	Yes	No	RFC 5789	Apply partial modifications to a resource.
DELETE	No	Yes	Optional	No	RFC 9110	Remove the target resource.
HEAD	Yes	Yes	No	Yes	RFC 9110	Identical to GET but the server only returns headers — no body.
OPTIONS	Yes	Yes	Optional	No	RFC 9110	Describe the communication options for the target resource.
CONNECT	No	No	No	No	RFC 9110	Establish a tunnel to the server identified by the target resource.
TRACE	Yes	Yes	No	No	RFC 9110	Perform a loop-back test along the path to the target resource.

HTTP method properties explained

Safemethods (GET, HEAD, OPTIONS, TRACE) don't modify server state — they're read-only. Idempotentmethods can be called multiple times with the same result — PUT, DELETE, GET, HEAD, and OPTIONS are all idempotent. PATCH is not guaranteed idempotent because a patch document may apply incremental changes (e.g. "add 1 to counter"). Cacheable means browsers and proxies may store and reuse the response.

For more HTTP tools see HTTP Status Codes, cURL Command Builder, and JWT Decoder.

Private & free — this tool runs entirely in your browser.