HTTP status codes
Every HTTP status code, filterable.
HTTP status codes
| Code | Name | Meaning |
|---|---|---|
| 100 | Continue | The server has the request's headers and the client should go on and send the body. |
| 101 | Switching Protocols | The server agrees to change protocol, as for a WebSocket upgrade. |
| 102 | Processing | WebDAV: the server has the request and is still working on it. |
| 103 | Early Hints | Headers the client can start preloading from while the final response is prepared. |
| 200 | OK | The request worked. What comes back depends on the method. |
| 201 | Created | The request worked and made a new resource, usually named in the Location header. |
| 202 | Accepted | The request was accepted for processing that has not finished. |
| 203 | Non-Authoritative Information | The response comes from a proxy that changed the origin server's answer. |
| 204 | No Content | It worked and there is nothing to send back. |
| 205 | Reset Content | It worked; the client should clear the form or view that sent it. |
| 206 | Partial Content | Only the byte range that was asked for, as in a resumed download. |
| 207 | Multi-Status | WebDAV: several results in one response. |
| 301 | Moved Permanently | The resource has a new address for good. Clients and search engines should use it from now on. |
| 302 | Found | The resource is at another address for now. Keep using the original next time. |
Runs in your browser: what you type or paste here is never sent to Hominin. You can also search for it: http status codes.