HTTP Methods: Explained

HTTP Methods Explained

Every HTTP request method in one table: method, safe, idempotent, request body, and typical use. The quick-reference companion to the HTTP Methods tool.

HTTP methods tell the server what action to take. Two properties matter most. Safe means the method does not change server state, so a GET or HEAD never writes data on its own. Idempotent means the result is the same no matter how many times you send the request, so a PUT or DELETE repeated ten times ends in the same state as once. POST is neither safe nor idempotent, which is why it is used to create new things. The companion tool lets you inspect each method in depth.

9 of 9 rows


HTTP methods
	Yes	Yes	No	Fetch a resource from the server without changing its state.
	No	No	Usually	Submit data to create a new resource or trigger an action.
	No	Yes	Yes	Replace the full resource at a known URL with the data you send.
	No	No	Yes	Apply a partial change to an existing resource.
	No	Yes	No	Remove a resource from the server.
	Yes	Yes	No	Get the response headers for a URL, like a GET that returns no body.
	Yes	Yes	No	Ask which methods and features the server allows for a URL.
	Yes	Yes	No	Loop the received request back for diagnostic testing of the path.
	No	No	No	Open a tunnel to a server, typically for TLS through a proxy.