HTTP status codes - the ones you actually meet. 1xx informational 100 Continue client may send the request body 101 Switching Protocols e.g. upgrade to WebSocket 2xx success 200 OK standard success 201 Created resource created; Location header points to it 202 Accepted queued for processing, not finished 204 No Content success, empty body 3xx redirection 301 Moved Permanently update bookmarks; method may change to GET 302 Found temporary redirect; method may change to GET 303 See Other go GET this other URL (typical after a form POST) 304 Not Modified cached copy is still valid 307 Temporary Redirect like 302 but the method must not change 308 Permanent Redirect like 301 but the method must not change 4xx client error 400 Bad Request malformed syntax or invalid parameters 401 Unauthorized authentication required or failed 403 Forbidden authenticated (or not) but not allowed 404 Not Found no such resource 405 Method Not Allowed e.g. POST to a GET-only URL; see the Allow header 406 Not Acceptable cannot produce the format asked for in Accept 408 Request Timeout client was too slow sending the request 409 Conflict state conflict, e.g. edit collision 410 Gone removed for good 413 Content Too Large request body too big 414 URI Too Long request URL too long 415 Unsupported Media Type 422 Unprocessable Content syntax fine, content invalid 429 Too Many Requests rate limited; see Retry-After 5xx server error 500 Internal Server Error generic server failure 501 Not Implemented method not supported by the server 502 Bad Gateway upstream server sent an invalid response 503 Service Unavailable overloaded or down for maintenance; see Retry-After 504 Gateway Timeout upstream server did not answer in time Rule of thumb: retry 408, 429, 502, 503 and 504 with backoff; do not retry other 4xx codes unchanged.
Or: /edit?page=HttpStatusCodes&text=your+text&name=YourName
Index | Recent changes | permalink | rev a6cc18ef1b78