HTTP 2xx
200 OK
The request succeeded. This is the normal response for a healthy page or API.
What causes it
- The request completed and the server returned the expected content.
How to fix it
Nothing to fix. Note that an API can return 200 while its body still reports an error, which is why response-body assertions matter.
Example response
A typical raw HTTP response a client receives for a 200, with the headers this code is defined around.
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8Related codes
201
CreatedThe request succeeded and a new resource was created as a result.202
AcceptedThe request was accepted for processing, but the processing has not finished. Common for async or queued work.204
No ContentThe request succeeded but there is no content to return.206
Partial ContentThe server is delivering only part of the resource, in response to a Range request.Know before your visitors do.
Sentinel checks your site around the clock from multiple regions and alerts you the moment it starts returning a 2xx error, so you can fix it before it costs you.