Everything's okay so far, keep going with the request.
The server will switch to the protocol you asked for.
The server has received and is processing the request, but no response is available yet.
Hints are available, you can use them for preloading if you like.
The request has succeeded.
The request has succeeded and has led to the creation of a resource.
The request has been accepted for processing, but hasn't been completed. Maybe it will be, maybe it won't.
Request accepted, but the payload has been modified from the 200 OK
response.
Request succeeded, and you don't need to navigate away.
You should reset the document view. Clear any form data, reset canvases, refresh the UI.
Here's the data you asked for. Their may be more.
There might be mixture of responses.
Used in a 207 Multi-Status
response to save space and avoid conflicts.
An instance manipulation (IM) delta has been returned.
There's more than one possible responses, you'll need to choose one of them.
The requested resource has been definitively moved to the URL given by the Location
headers. A browser redirects to the new URL and search engines update their links to the resource.
The resource requested has been temporarily moved to the URL given by the Location
header.
The redirects don't link to the requested resource itself, but to another resource.
Nothing has changed since your last request, there is no need to retransmit the requested resources.
The 305 (Use Proxy)
status code was defined in a previous version of this specification and is now deprecated.
No longer used. Originally meant 'Subsequent requests should use the specified proxy.'
What you're looking for has moved, but only temporarily.
What you're looking for has moved, permanently.
That request won't be processed, you need to adjust the request.
You're not authorised to get the response.
Cash upfront, no tick.
Nope, the server isn't let you have that.
What you're asking for can't be found (or, at least the server is claiming that).
What you're trying to do isn't valid.
What you're asking for can't be provided.
The client needs to authenticate itself in order to use a proxy.
The connection's unused and will be closed.
What you're asking for conflicts with the servers current state.
The requested resources is no longer available, that probably won't change.
You forgot the Content-Length
header.
The required conditions have not been met.
Too much data sent, rejecting.
The request is a bit long, shorten it.
Your payload format isn't supported.
What you've asked for isn't available, try again.
The expectation given in the request's Expect
header could not be met.
Any attempt to brew coffee with a teapot should result in the error code '418 I'm a teapot'. The resulting entity body may be short and stout.
You're asking the wrong server.
What you're asking for can't be processed.
The resource is locked.
The request has a dependency that has not been met.
The request will not be processed, it looks suspicious.
If you upgrade your request, it may work.
You need to condition the request.
You're asking for too much, slow down.
The request's HTTP headers are too long.
The user requested a resource that is not available due to legal reasons, such as a web page for which a legal action has been issued.
The server's so stuffed, it can't even tell you why it's stuffed.
What you're asking for is not supported.
A server further down the chain provided an invalid response.
Server is overloaded or down for maintenance.
A server further down the chain didn't respond in a timely manner.
The server will not accept the clients HTTP version.
The content you've requested requires negotiation.
The server doesn't have enough space to process your request.
Infinite loop detected.
The HTTP Extension Framework has not been extended by the server.
The client needs to authenticate to gain network access.