-as of [17 APRIL 2024]–
.
4xx client errors
A The Wikimedia 404 message
This class of status code is intended for situations in which the error seems to have been caused by the client.
Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
These status codes are applicable to any request method.
User agents should display any included entity to the user
.
400
Bad Request
The server cannot or will not process the request due to an apparent client error
(e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routine))
.
.
401
Unauthorized
(RFC 7235)
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource.
See Basic access authentication and Digest access authentication
401 semantically means “unauthorised”, the user does not have valid authentication credentials for the target resource.
Note
Some sites incorrectly issue HTTP 401 when an IP address is banned from the website (usually the website domain) and that specific address is refused permission to access a website
.
.
402
Payment Required
Reserved for future use.
The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, as proposed, for example, by GNU Taler,[34] but that has not yet happened, and this code is not widely used.
Google Developers API uses this status if a particular developer has exceeded the daily limit on requests
Sipgate uses this code if an account does not have sufficient funds to start a call
Shopify uses this code when the store has not paid their fees and is temporarily disabled.
Stripe uses this code for failed payments where parameters were correct, for example blocked fraudulent payments
.
.
403
Forbidden
The request contained valid data and was understood by the server, but the server is refusing action.
This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action
(e.g. creating a duplicate record where only one is allowed).
This code is also typically used if the request provided authentication by answering the WWW-Authenticate header field challenge, but the server did not accept that authentication.
The request should not be repeated
.
.
404
Not Found
The requested resource could not be found but may be available in the future.
Subsequent requests by the client are permissible
.
.
405
Method Not Allowed
A request method is not supported for the requested resource;
for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource
.
.
406
Not Acceptable
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request
See Content negotiation
.
.
407
Proxy Authentication Required
(RFC 7235)
The client must first authenticate itself with the proxy
.
.
408
Request Timeout
The server timed out waiting for the request.
According to HTTP specifications:
“The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time”
.
.
409
Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource, such as an edit conflict between multiple simultaneous updates
.
.
410
Gone
Indicates that the resource requested is no longer available and will not be available again.
This should be used when a resource has been intentionally removed and the resource should be purged.
Upon receiving a 410 status code, the client should not request the resource in the future.
Clients such as search engines should remove the resource from their indices
Most use cases do not require clients and search engines to purge the resource, and a “404 Not Found” may be used instead
.
.
411
Length Required
The request did not specify the length of its content, which is required by the requested resource
.
.
412
Precondition Failed
(RFC 7232)
The server does not meet one of the preconditions that the requester put on the request header fields
.
.
413
Payload Too Large
(RFC 7231)
The request is larger than the server is willing or able to process.
Previously called “Request Entity Too Large”
.
.
414
URI Too Long
(RFC 7231)
The URI provided was too long for the server to process.
Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request
Called “Request-URI Too Long” previously
.
.
415
Unsupported Media Type
(RFC 7231)
The request entity has a media type which the server or resource does not support.
For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format
.
.
416
Range Not Satisfiable
(RFC 7233)
The client has asked for a portion of the file (byte serving), but the server cannot supply that portion.
For example, if the client asked for a part of the file that lies beyond the end of the file
Called “Requested Range Not Satisfiable” previously
.
417
Expectation Failed
The server cannot meet the requirements of the Expect request-header field
.
.
418
I’m a teapot
(???)
(RFC 2324, RFC 7168)
This code was defined in 1998 as one of the traditional IETF April Fools’ jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.
The RFC specifies this code should be returned by teapots requested to brew coffee
This HTTP status is used as an Easter egg in some websites
(such as Google.com’s “I’m a teapot” easter egg)
.
.
421
Misdirected Request
(RFC 7540)
The request was directed at a server that is not able to produce a response
(for example because of connection reuse)
.
.
422
Unprocessable Entity
(WebDAV; RFC 4918)
The request was well-formed but was unable to be followed due to ‘semantic errors’
.
.
423
Locked
(WebDAV; RFC 4918)
The resource that is being accessed is locked
.
.
424
Failed Dependency
(WebDAV; RFC 4918)
The request failed because it depended on another request and that request failed
(e.g., a PROPPATCH)
.
.
425
Too Early
(RFC 8470)
Indicates that the server is unwilling to risk processing a request that might be replayed
.
426
Upgrade Required
The client should switch to a different protocol such as TLS/1.3, given in the Upgrade header field
.
428
Precondition Required
(RFC 6585)
The origin server requires the request to be conditional.
Intended to prevent the ‘lost update’ problem, where a client GETs a resource’s state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict
.
429
“Too Many Requests”
(RFC 6585)
The user has sent too many requests in a given amount of time.
Intended for use with ‘rate-limiting schemes’
In computer networks, rate limiting is used to control the rate of requests sent or received by a network interface controller. It can be used to prevent DoS attacks and limit web scraping
.
*our reports* –>
(shows up when i link ‘instagram’ from ‘wordpress site’)
(because you need to log into ‘instagram’ before viewing profiles)
.
.
431
Request Header Fields Too Large
(RFC 6585)
The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large
.
451
“Unavailable For Legal Reasons”
(RFC 7725)
A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource
The code 451 was chosen as a reference to the novel Fahrenheit 451
(see the Acknowledgements in the RFC)
.
.
*UNOFFICIAL CODES* –>
419
Page Expired
(Laravel Framework)
Used by the Laravel Framework when a CSRF Token is missing or expired
.
.
420
Method Failure
(Spring Framework)
A deprecated response used by the Spring Framework when a method has failed
.
.
420
Enhance Your Calm
(Twitter)
Returned by version 1 of the ‘Twitter Search’ + ‘Trends API’ when the client is being ‘rate limited’
versions 1.1 and later use the 429 Too Many Requests response code instead
The phrase “Enhance your calm” comes from the 1993 movie Demolition Man, and its association with this number is likely a reference to ‘cannabis’
.
.
430
Request Header Fields Too Large
(Shopify)
Used by Shopify, instead of the 429 Too Many Requests response code,
when too many URLs are requested within a certain time frame
.
.
450
Blocked by Windows Parental Controls (Microsoft)
The Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the requested webpage
.
.
498
Invalid Token (Esri)
Returned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token.[77]
499 Token Required (Esri)
Returned by ArcGIS for Server. Code 499 indicates that a token is required but was not submitted
.
Internet Information Services
Microsoft’s Internet Information Services (IIS) web server expands the 4xx error space to signal errors with the client’s request
.
When ProxyErrorOverride is enabled in Apache, response bodies that contain a status code of 4xx or 5xx are automatically discarded by Apache in favor of a generic response or a custom response specified by the ErrorDocument directive
.
.
440
Login Time-out
The client’s session has expired and must log in again
.
.
449
Retry With
The server cannot honour the request because the user has not provided the required information.[83]
.
.
451
redirect
Used in Exchange ActiveSync when either a more efficient server is available or the server cannot access the users’ mailbox
The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server
IIS sometimes uses additional decimal sub-codes for more specific information,[86] however these sub-codes only appear in the response payload and in documentation, not in the place of an actual HTTP status code.
nginx
The nginx web server software expands the 4xx error space to signal issues with the client’s request
.
.
444
No Response
Used internally[89] to instruct the server to return no information to the client and close the connection immediately
.
.
494
Request header too large
Client sent too large request or too long header line
.
.
495
SSL Certificate Error
An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate.
.
.
496
SSL Certificate Required
An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided
.
.
497
HTTP Request Sent to HTTPS Port
An expansion of the 400 Bad Request response code, used when the client has made a HTTP request to a port listening for HTTPS requests
.
.
499
Client Closed Request
Used when the client has closed the request before the server could send a response
.
AWS Elastic Load Balancer
Amazon’s Elastic Load Balancing adds a few custom 4xx return codes
.
.
460
Client closed the connection with the load balancer before the idle timeout period elapsed.
Typically when client timeout is sooner than the Elastic Load Balancer’s timeout
.
463
The load balancer received an X-Forwarded-For request header with more than 30 IP addresses\
.
.
*👨🔬🕵️♀️🙇♀️*SKETCHES*🙇♂️👩🔬🕵️♂️*
.
.
.
.
💕💝💖💓🖤💙🖤💙🖤💙🖤❤️💚💛🧡❣️💞💔💘❣️🧡💛💚❤️🖤💜🖤💙🖤💙🖤💗💖💝💘
.
.
🔥🔥🔥🔥🔥🔥*we won the war* 🔥🔥🔥🔥🔥🔥