HTTP/HTTPS Status Codes
A webserver can return these status codes
HTTP Status 200
2xx – OK/SUCCESS (Nothing is wrong.)
- 200 OK – Standard response for successful HTTP requests
- 201 Created – Request has been fulfilled; new resource created
- 202 Accepted – Request accepted, processing pending
- 203 Non-Authoritative Information – Request processed, information may be from another source
- 204 No Content – Request processed, no content returned
- 205 Reset Content – Eequest processed, no content returned, reset document view
- 206 Partial Content – Partial resource return due to request header
- 207 Multi-Status – XML, can contain multiple separate responses
- 208 Already Reported – Results previously returned
- 226 IM Used – Request fulfilled, reponse is instance-manipulations
HTTP Status 300
3xx – REDIRECTION (Something has happened.)
- 300 Multiple Choices – Multiple options for the resource delivered
- 301 Moved Permanently – This and all future requests directed to the given URI
- 302 Found – Temporary response to request found via alternative URI
- 303 See Other – Permanent response to request found via alternative URI
- 304 Not Modified – Resource has not been modified since last requested
- 305 Use Proxy – Content located elsewhere, retrieve from there
- 306 Reserved – Subsequent requests should use the specified proxy
- 307 Temporary Redirect – Connect again to different URI as provided
- 308 Permanent Redirect – Resumable HTTP requests
HTTP Status 400
4xx – CLIENT ERROR (You have an error.)
- 400 Bad Request – Request cannot be fulfilled due to bad syntax
- 401 Unauthorized – Authentication is possible but has failed
- 402 Payment Required – Payment required, reserved for future use
- 403 Forbidden – Server refuses to respond to request
- 404 Not Found – Requested resource could not be found
- 405 Method Not Allowed – Request method not supported by that resource
- 406 Not Acceptable – Content not acceptable according to the Accept headers
- 407 Proxy Authentication Required – Client must first authenticate itself with the proxy
- 408 Request Timeout – Server timed out waiting for the request
- 409 Conflict – Request could not be processed because of conflict
- 410 Gone – Resource is no longer available and will not be available again
- 411 Length Required – Request did not specify the length of its content
- 412 Precondition Failed – Server does not meet request preconditions
- 413 Request Entity Too Large – Request is larger than the server is willing or able to process
- 414 Request-URI Too Long – URI provided was too long for the server to process
- 415 Unsupported Media Type – Server does not support media type
- 416 Requested Range Not Satisfiable – Client has asked for unprovidable portion of the file
- 417 Expectation Failed – Server cannot meet requirements of Expect request-header field
- 422 Unprocessable Entity – Request unable to be followed due to semantic errors
- 423 Locked – Resource that is being accessed is locked
- 424 Failed Dependency – Resource that is being accessed is locked
- 426 Upgrade Required – Client should switch to a different protocol
- 428 Precondition Required – Origin server requires the request to be conditional
- 429 Too Many Requests – User has sent too many requests in a given amount of time
- 431 Request Header Fields Too Large – Server is unwilling to process the request
HTTP Status 500
5xx – SERVER ERROR (The website has an error.)
- 500 Internal Server Error – Generic error message
- 501 Not Implemented – Server does not recognise method or lacks ability to fulfill
- 502 Bad Gateway – Server received an invalid response from upstream server
- 503 Service Unavailable – Server is currently unavailable
- 504 Gateway Timeout – Gateway did not receive response from upstream server
- 505 HTTP Version Not Supported – Server does not support the HTTP protocol version
- 506 Variant Also Negotiates (Experimental) – Content negotiation for the request results in a circular reference
- 507 Insufficient Storage – Server is unable to store the representation
- 508 Loop Detected – Server detected an infinite loop while processing the request
- 509 Unassigned – Bandwidth limit exceeded
- 510 Not Extended – Further extensions to the request are required
- 511 Network Authentication Required – Client needs to authenticate to gain network access
- CLOUDFLARE SPECIFIC 5XX ERROR CODES:
- 520 Web server is returning an unknown error -
- 521 Web server is down – The server is powered off. Perhaps in the middle of rebooting.
- 522 Connection timed out -
- 523 Origin Unreachable -
- 524 Timeout – The server is not responding. It probably needs rebooting.
- 525 SSL handshake failed -
- 526 Invalid SSL certificate -
Cloudflare Specific
- 1020 Access denied - Similar to a 403 Error. Traffic was blocked by a security setting within Cloudflare. Likely a Firewall rule.