Http Status Codes
The list of all HTTP status codes, their name, and their meaning.
1XX informational response
100
Continue
Client can continue with the request.
101
Switching protocols
Protocols are switching as requested by the client.
102
Processing
Server is processing the request but no response is available yet.
103
Early hints
Server provides hints to the client to preload resources before the final response.
2XX success
200
Ok
Request succeeded.Resource returned.
201
Created
Resource successfully created.
202
Accepted
Request accepted, but not yet processed.
203
Non-Authoritative Information
Information returned from a third-party source.
204
No Content
Request succeeded, but no content returned.
205
Reset Content
Client should reset the document view.
206
Partial Content
Partial resource returned, often used for downloads.
207
Multi-Status
Provides the statuses of multiple resources, depending on how many sub-requests were made.
208
Already Reported
The members of a DAV element have already been listed and won’t be included (repeated) again.
226
IM Used
The server completed a GET request. And the response indicates one or more instance-manipulation in results.
3XX redirection
300
Multiple Choices
Request has multiple possible responses.
301
Moved Permanently
The target resource has a new permanent URL.All future references will be redirected to that new URL.
302
Found
The requested resource has temporarily moved to a new URL.
303
See Other
Resource has permanently moved to a new URL. The browser displays the new URL.
304
Not Modified
The response is unchanged, so the client can use the cached version of the resource.
305
Use Proxy
The requested resource is available only through a proxy, the address for which is provided in the response.
306
Switch Proxy
No longer used. Originally meant "Subsequent requests should use the specified proxy."
307
Temporary Redirect
The request should be repeated with a different URI, but future requests should continue to use the original URI.
308
Permanent Redirect
The request and all future requests should be repeated using another URI.
4XX client error
400
Bad Request
The server can’t or won’t process the request due to a client error.
401
Unauthorized
The user doesn’t have valid authentication credentials to get the requested resource.
402
Payment Required
Reserved for future use, this code was initially intended for digital payment systems but is rarely used and lacks a standard convention.
403
Forbidden
The client doesn’t have access rights to the content.
404
Not Found
The server can’t find the requested resource, and no redirection has been set.
405
Method Not Allowed
A request method is not supported for the requested resource.
406
Not Acceptable
The server doesn’t find any content that satisfies the criteria given according to the Accept headers requested.
407
Proxy Authentication Required
A client must must authenticate the proxy before continue.
408
Request Timeout
The server timed out waiting for the request.
409
Conflict
The server can’t fulfill the request because there’s a conflict with the resource.
410
Gone
The content requested has been permanently deleted from the server and will not be reinstated in future.
411
Length Required
The server rejects the request because it requires a defined content-Length header field.
412
Precondition Failed
The resource has preconditions in the header fields that the given data fails to meet.
413
Payload Too Large
The client’s request is larger than the server’s defined limits, and the server refuses to process it.
414
URI Too Long
The URI provided was too long for the server to process.
415
Unsupported Media Type
The request entity has a media type which the server or resource does not support.
416
Range Not Satisfiable
The server can’t fulfill the value indicated in the request’s Range header field.
417
Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
418
I’m a teapot
The server refuses the attempt to brew coffee with a teapot.
421
Misdirected Request
A request to a server that can’t produce a response.
422
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
423
Locked
The resource that is being accessed is locked.
424
Failed Dependency
The request failed due to previous requests.
425
Too Early
The server is unwilling to process a request that might be replayed.
426
Update Required
It indicates that the client should upgrades to a different protocol.
428
Precondition Required
The server needs the request to be conditional.
429
Too Many Requests
The user has sent too many requests in a given amount of time.
431
Request Header Fields Too Large
The server can’t process the request because the header fields are too large.
451
Unavailable For Legal Reasons
The user requests a resource the server can’t legally provide.
5XX server error
500
Internal Server Error
The server has encountered an unexpected error and cannot complete the request.
501
Not Implemented
The server can’t fulfill the request or doesn’t recognize the request method.
502
Bad Gateway
503
Service Unavailable
The server is unable to process the request. This often occurs when a server is overloaded or down for maintenance.
504
Gateway Timeout
The server was acting as a gateway or proxy and timed out, waiting for a response.
505
HTTP Version Not Supported
The server doesn’t support the HTTP version in the request.
506
Variant Also Negotiates
The server has an internal configuration error.
507
Insufficient Storage
The server is unable to store the representation needed to complete the request.
508
Loop Detected
The server detected an infinite loop while processing the request.
510
Not Extended
Further extensions to the request are required for the server to fulfill it.
511
Network Authentication Required
The client needs to authenticate to gain network access.
