tool::http-status-detail
200 OK
The request has succeeded.
Status Code
200
Name
OK
Category
2xxDetailed Explanation
HTTP 200 OK is the most fundamental success status code indicating that the client's request was processed successfully. For GET requests, the resource is included in the response body; for POST requests, the result of the operation is returned. It is the most commonly received response code by both web browsers and API clients.
Common Causes
- ▸A resource was successfully retrieved via a GET request
- ▸A POST request was processed successfully
- ▸A resource update via PUT/PATCH was completed
- ▸A HEAD request confirmed the existence of a resource
How to Fix
- 1.200 is a normal response, so no fix is needed
- 2.Use 201 Created instead of 200 when creating a new resource
- 3.If there is no response body, 204 No Content is more appropriate
- 4.Include ETag and Last-Modified headers to enable caching
Related HTTP Headers
Content-TypeContent-LengthETagCache-ControlLast-ModifiedResponse Example
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 27
{"status":"ok","id":12345}Related Status Codes
201CreatedThe request has been fulfilled and a new resource has been created.→202AcceptedThe request has been accepted but not yet acted upon.→203Non-Authoritative InformationThe response is from a transforming proxy, not the origin server.→204No ContentThe server successfully processed the request but returns no content.→205Reset ContentThe server processed the request; the client should reset the document view.→
ad · 300×250
// related tools