HTTP Protocol Reference & Checker
HTTP status codes
- 100Continue
The server got the start of the request and is waiting for the rest.
- 101Switching Protocols
The server agrees to switch to another protocol, such as a WebSocket.
- 103Early Hints
The server sends hints about files the page will need before the real reply is ready.
- 200OK
It worked. The reply has what was asked for.
- 201Created
Something new was made, such as a new account or record.
- 202Accepted
The request was received and will be handled later.
- 204No Content
It worked, and there is nothing to send back.
- 206Partial Content
Only part of the file was sent, as asked. Used for video and resumed downloads.
- 301Moved Permanently
The page has a new address for good. Browsers and search engines remember it.
What to do: Update your links to the new address.
- 302Found
The page is somewhere else for now. Keep using the old address.
- 303See Other
The result is at another address. Fetch it with a plain GET.
- 304Not Modified
Nothing changed since last time, so the saved copy is still good.
- 307Temporary Redirect
Go to another address for now, and repeat the request the same way.
- 308Permanent Redirect
Moved for good, and the request is repeated the same way.
- 400Bad Request
The server could not understand the request.
What to do: Check the address, the data you send, and that JSON is valid.
- 401Unauthorized
You need to sign in first, or the sign-in details are wrong.
What to do: Send a valid token or password. Check it has not run out.
- 402Payment Required
Payment is needed. Rarely used, but some services use it for plan limits.
- 403Forbidden
The server knows who you are but will not let you in.
What to do: Check your permissions, file access rules and any firewall.
- 404Not Found
Nothing exists at this address.
What to do: Check for typos, and that the page or file was not moved or deleted.
- 405Method Not Allowed
That kind of request (GET, POST...) is not allowed here.
What to do: Use a method the page supports. The Allow header lists them.
- 406Not Acceptable
The server cannot reply in any format you said you accept.
- 408Request Timeout
The server waited too long for the request to arrive.
What to do: Try again, and check the connection.
- 409Conflict
The request clashes with the current state, such as a name that is already taken.
- 410Gone
It used to be here and has been removed for good.
- 411Length Required
The server needs to know how big the request is.
- 412Precondition Failed
A condition in your request headers was not met.
- 413Content Too Large
What you sent is bigger than the server accepts.
What to do: Send a smaller file, or raise the upload limit on the server.
- 414URI Too Long
The web address is too long for the server.
- 415Unsupported Media Type
The server does not accept this kind of data.
What to do: Set the right Content-Type header.
- 416Range Not Satisfiable
The part of the file you asked for does not exist.
- 418I'm a teapot
A joke code from 1998. A teapot cannot make coffee.
- 422Unprocessable Content
The request made sense but the data failed checks, such as a missing field.
What to do: Read the error text for which fields to fix.
- 423Locked
The thing you want is locked.
- 425Too Early
The server will not risk handling a request that might be replayed.
- 426Upgrade Required
Switch to a newer protocol and try again.
- 428Precondition Required
The server needs the request to include a condition, to avoid overwriting changes.
- 429Too Many Requests
You sent too many requests in a short time.
What to do: Slow down and retry after the time in the Retry-After header.
- 431Header Fields Too Large
The headers are too big, often because of huge cookies.
What to do: Clear cookies for the site.
- 451Unavailable For Legal Reasons
The page is blocked because of a legal demand.
- 500Internal Server Error
Something broke on the server. It is not your fault.
What to do: Check the server logs. If you are a visitor, try again later.
- 501Not Implemented
The server does not support what you asked for.
- 502Bad Gateway
A server in the middle got a bad reply from the one behind it.
What to do: Check the app behind the front server is running.
- 503Service Unavailable
The server is busy or down for maintenance.
What to do: Wait and try again. Check the Retry-After header.
- 504Gateway Timeout
A server in the middle waited too long for the one behind it.
What to do: Look for slow code or a database stuck on the server.
- 505HTTP Version Not Supported
The server does not support this version of HTTP.
- 507Insufficient Storage
The server has run out of space.
- 511Network Authentication Required
You must sign in to the network first, like café Wi-Fi.
Questions
Do I need an account to use the http protocol reference & checker?
No. It works the moment the page loads. An account is optional and only adds saving and syncing across devices.
Does my data leave my device?
No. HTTP Protocol Reference & Checker runs entirely in your browser, so what you enter is never uploaded.
Is the http protocol reference & checker free?
Yes. It is free to use, with no sign-up, trial or usage wall.