Example 1: 200 status code
100 Continue [RFC7231, Section 6.2.1]
101 Switching Protocols [RFC7231, Section 6.2.2]
102 Processing [RFC2518]
103 Early Hints [RFC8297]
104-199 Unassigned
200 OK [RFC7231, Section 6.3.1]
201 Created [RFC7231, Section 6.3.2]
202 Accepted [RFC7231, Section 6.3.3]
203 Non-Authoritative Information [RFC7231, Section 6.3.4]
204 No Content [RFC7231, Section 6.3.5]
205 Reset Content [RFC7231, Section 6.3.6]
206 Partial Content [RFC7233, Section 4.1]
207 Multi-Status [RFC4918]
208 Already Reported [RFC5842]
209-225 Unassigned
226 IM Used [RFC3229]
227-299 Unassigned
300 Multiple Choices [RFC7231, Section 6.4.1]
301 Moved Permanently [RFC7231, Section 6.4.2]
302 Found [RFC7231, Section 6.4.3]
303 See Other [RFC7231, Section 6.4.4]
304 Not Modified [RFC7232, Section 4.1]
305 Use Proxy [RFC7231, Section 6.4.5]
306 (Unused) [RFC7231, Section 6.4.6]
307 Temporary Redirect [RFC7231, Section 6.4.7]
308 Permanent Redirect [RFC7538]
309-399 Unassigned
400 Bad Request [RFC7231, Section 6.5.1]
401 Unauthorized [RFC7235, Section 3.1]
402 Payment Required [RFC7231, Section 6.5.2]
403 Forbidden [RFC7231, Section 6.5.3]
404 Not Found [RFC7231, Section 6.5.4]
405 Method Not Allowed [RFC7231, Section 6.5.5]
406 Not Acceptable [RFC7231, Section 6.5.6]
407 Proxy Authentication Required [RFC7235, Section 3.2]
408 Request Timeout [RFC7231, Section 6.5.7]
409 Conflict [RFC7231, Section 6.5.8]
410 Gone [RFC7231, Section 6.5.9]
411 Length Required [RFC7231, Section 6.5.10]
412 Precondition Failed [RFC7232, Section 4.2][RFC8144, Section 3.2]
413 Payload Too Large [RFC7231, Section 6.5.11]
414 URI Too Long [RFC7231, Section 6.5.12]
415 Unsupported Media Type [RFC7231, Section 6.5.13][RFC7694, Section 3]
416 Range Not Satisfiable [RFC7233, Section 4.4]
417 Expectation Failed [RFC7231, Section 6.5.14]
418-420 Unassigned
421 Misdirected Request [RFC7540, Section 9.1.2]
422 Unprocessable Entity [RFC4918]
423 Locked [RFC4918]
424 Failed Dependency [RFC4918]
425 Too Early [RFC8470]
426 Upgrade Required [RFC7231, Section 6.5.15]
427 Unassigned
428 Precondition Required [RFC6585]
429 Too Many Requests [RFC6585]
430 Unassigned
431 Request Header Fields Too Large [RFC6585]
432-450 Unassigned
451 Unavailable For Legal Reasons [RFC7725]
452-499 Unassigned
500 Internal Server Error [RFC7231, Section 6.6.1]
501 Not Implemented [RFC7231, Section 6.6.2]
502 Bad Gateway [RFC7231, Section 6.6.3]
503 Service Unavailable [RFC7231, Section 6.6.4]
504 Gateway Timeout [RFC7231, Section 6.6.5]
505 HTTP Version Not Supported [RFC7231, Section 6.6.6]
506 Variant Also Negotiates [RFC2295]
507 Insufficient Storage [RFC4918]
508 Loop Detected [RFC5842]
509 Unassigned
510 Not Extended [RFC2774]
511 Network Authentication Required [RFC6585]
512-599 Unassigned
source : https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml
Example 2: http response status codes
HTTP response status codes
HTTP response status codes indicate whether a specific HTTP request has been successfully completed.
Responses are grouped in five classes:
1. Informational responses (100–199)
2. Successful responses (200–299)
3. Redirects (300–399)
4. Client errors (400–499)
5. Server errors (500–599)
1. Information responses
a. 100 Continue
b. 101 Switching Protocol
c. 102 Processing (WebDAV)
d. 103 Early Hints
2. Successful responses
a. 200 OK
b. 201 Created
c. 202 Accepted
d. 203 Non-Authoritative Information
e. 204 No Content
f. 205 Reset Content
g. 206 Partial Content
h. 207 Multi-Status (WebDAV)
i. 208 Already Reported (WebDAV)
j. 226 IM Used (HTTP Delta encoding)
3. Redirection messages
a. 300 Multiple Choice
b. 301 Moved Permanently
c. 302 Found
d. 303 See Other
e. 304 Not Modified
f. 305 Use Proxy
g. 306 unused
h. 307 Temporary Redirect
i. 308 Permanent Redirect
4. Client error responses
a. 400 Bad Request
b. 401 Unauthorized
c. 402 Payment Required
d. 403 Forbidden
e. 404 Not Found
f. 405 Method Not Allowed
g. 406 Not Acceptable
h. 407 Proxy Authentication Required
i. 408 Request Timeout
j. 409 Conflict
k. 410 Gone
l. 411 Length Required
m. 412 Precondition Failed
n. 413 Payload Too Large
o. 414 URI Too Long
p. 415 Unsupported Media Type
q. 416 Range Not Satisfiable
r. 417 Expectation Failed
s. 418 I'm a teapot
t. 421 Misdirected Request
u. 425 Too Early
v. 426 Upgrade Required
w. 428 Precondition Required
x. 429 Too Many Requests
y. 431 Request Header Fields Too Large
z. 451 Unavailable For Legal Reasons
5. Server error responses
a. 500 Internal Server Error
b. 501 Not Implemented
c. 502 Bad Gateway
d. 503 Service Unavailable
e. 504 Gateway Timeout
f. 505 HTTP Version Not Supported
g. 506 Variant Also Negotiates
h. 507 Insufficient Storage (WebDAV)
i. 508 Loop Detected (WebDAV)
j. 510 Not Extended
k. 511 Network Authentication Required
Example 3: server 200 response
status code 200 OK. The request has succeeded.
Example 4: http status codes
Some important http status codes are:
200: The one you will mostly want to get. Succesful transfer
301: Moved Permanently. 300 defines Redirections
404: Not found. 400: bad requests as 401 Unauthorized and 403 Forbidden.
502: Bad Gateway. 500 defines Internal Server Errors.
Example 5: 200 error code
The HTTP 200 OK success status response code indicates that the request has succeeded. A 200 response is cacheable by default. The meaning of a success depends on the HTTP request method: GET : The resource has been fetched and is transmitted in the message body.
from developer.mozilla.org