ffee All tools
EN 中文 FR DE

HTTP Method Reference

Every standard HTTP method with its safety, idempotency and body behaviour in one searchable table.

Search HTTP methods

Showing 0 methods
Safety and idempotency follow the HTTP semantics defined in RFC 9110.

How to use the HTTP Method Reference

  1. Type a method name or a keyword such as safe or idempotent.
  2. Read across the row for the body behaviour of that method.
  3. Use the table to check whether a request can be retried safely.

Features

Advertisement

More tools

Cron Expression Generator Cron Expression Explainer Regex Cheatsheet Git Command Reference SQL Keyword Reference CSS Property Reference HTML Tag Reference ASCII Table Unicode Character Lookup Keyboard Key Codes CSS Units Reference HTTP Header Reference

Frequently Asked Questions

Common questions about the free online http method reference.

A safe method is read only, so it does not change the state of the server, and GET, HEAD, OPTIONS and TRACE are safe.
An idempotent request can be sent several times with the same effect on the server as sending it once.
PUT replaces the whole resource with the request body, while PATCH applies a partial modification only.
Use POST when the server decides the new resource identifier, and PUT when the client already knows the target URI.
No. A GET request should not carry a body, and any parameters belong in the query string.
OPTIONS asks which methods and headers the server supports for a resource, and it is used for CORS preflight.
TRACE echoes the request back and has been used for cross site tracing, so most servers disable it in production.
CONNECT asks a proxy to open a raw TCP tunnel, which is how HTTPS traffic passes through forward proxies.
GET, HEAD, OPTIONS, TRACE, PUT and DELETE can be retried, because repeating them leaves the same server state.

Last updated: October 10, 2026