Internal Server Error Wiki
Contents |
referer DNT X-Forwarded-For Status codes 301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451 Unavailable For Legal Reasons v t e
Http Error Code
This is a list of Hypertext Transfer Protocol (HTTP) response status codes. error code 500 It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes. error code list The first digit of the status code specifies one of five classes of response; an HTTP client must recognise these five classes at a minimum. The phrases used are the
Http Status Codes Cheat Sheet
standard wordings, but any human-readable alternative can be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).[1] The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.[2] Microsoft IIS sometimes uses additional decimal sub-codes to provide more specific information,[3] but not all of those are here (note that these sub-codes
Http Response
only appear in the response payload and in documentation; not in the place of an actual HTTP status code). Contents 1 1xx Informational 2 2xx Success 3 3xx Redirection 4 4xx Client Error 5 5xx Server Error 6 Unofficial codes 6.1 Internet Information Services 6.2 nginx 6.3 Cloudflare 7 See also 8 Notes 9 References 10 External links 1xx Informational[edit] Request received, continuing process. This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 client except under experimental conditions.[4] 100 Continue The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's
code via httpstatuses.com/code or browse the list below. @ http response example Share on Twitter★ Star on GitHub⊕ Add to Pinboard
Http 422
1×× Informational 100 Continue 101 Switching Protocols 102 Processing 2×× Success 200 OK http code 403 201 Created 202 Accepted 203 Non-authoritative Information 204 No Content 205 Reset Content 206 Partial Content 207 Multi-Status 208 Already Reported 226 https://en.wikipedia.org/wiki/List_of_HTTP_status_codes IM Used 3×× Redirection 300 Multiple Choices 301 Moved Permanently 302 Found 303 See Other 304 Not Modified 305 Use Proxy 307 Temporary Redirect 308 Permanent Redirect 4×× Client Error 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 404 Not Found 405 Method https://httpstatuses.com/ Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Request Timeout 409 Conflict 410 Gone 411 Length Required 412 Precondition Failed 413 Payload Too Large 414 Request-URI Too Long 415 Unsupported Media Type 416 Requested Range Not Satisfiable 417 Expectation Failed 418 I'm a teapot 421 Misdirected Request 422 Unprocessable Entity 423 Locked 424 Failed Dependency 426 Upgrade Required 428 Precondition Required 429 Too Many Requests 431 Request Header Fields Too Large 444 Connection Closed Without Response 451 Unavailable For Legal Reasons 499 Client Closed Request 5×× Server Error 500 Internal Server Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout 505 HTTP Version Not Supported 506 Variant Also Negotiates 507 Insufficient Storage 508 Loop Detected 510 Not Extended 511 Network Authentication Required 599 Network Connect Timeout Error
"500 Internal Server Error" is an HTTP status code and usually indicates a server misconfiguration or problem with a script. [edit] Server Configuration To check for configuration problems, rename any .htaccess file in http://x10hosting.com/wiki/500_Internal_Server_Error the folder or ancestor folder of the problematic webpage. If you can access http://www.restpatterns.org/HTTP_Status_Codes the resource after renaming an .htaccess file, then the .htaccess contains invalid entries. To figure out which configuration entries are causing the error, comment out sections until the error goes away, then uncomment sections until it returns. Once you've done this, look up the configuration directive(s) in Apache's documentation (or, if the directive configures error code an Apache extension, in the documentation for the extension) for the correct usage. If you're using the rewrite engine on shared hosting, make sure you have a "RewriteBase /" directive before any rewrite rules. [edit] Scripts If a script causes a 500 response but other resources in the same folder can be accessed, check the following: The script and any parent directory shouldn't be world writable. Check the internal server error script's permissions using your FTP client or cPanel. Furthermore, PHP scripts shouldn't have executable permissions set. On the other hand, non-PHP scripts (not currently enabled on the free servers) must be executable as well as start with a shebang line referencing the correct interpreter. At a minimum, a script must generate a Content-Type header and a blank line which ends the header section in order to comply with the CGI specification. PHP will generate the Content-Type header and ensure the blank line is present; other script interpreters won't. Additional headers are allowed, but the blank line must be present. Absence of a blank line will cause a 500 response. Run the script from the command line of your own computer to check whether it generates a blank line after any headers. Error messages from script errors (such as syntax errors) may print in the header section, often causing a 500 response. If you get error messages when you run a script on your own computer, fix the errors and test the updated script. PHP will always finish the header section before printing error messages (which can cause other errors). Some text editors will insert a non-printing character called a "byte or
Successful3xx - Redirection4xx - Client Error5xx - Server Error HTTP Status Codes Last modified 22:51, 22 May 2012 Table of contents1xx - Informational2xx - Successful3xx - Redirection4xx - Client Error5xx - Server Error Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required in the response. 1xx - Informational This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) 100 - Continue101 - Switching Protocols 2xx - Successful This class of status code indicates that the client's request was successfully received, understood, and accepted. 200 - OK201 - Created202 - Accepted203 - Non-Authoritative Information204 - No Content205 - Reset Content206 - Partial Content207 - Multi-Status 3xx - Redirection This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection. Note: previous versions of this specification recommended a maximum of five redirections. Content developers should be aware that there might be clients that implement such a fixed limitation. 300 - Multiple Choices301 - Moved Permanently302 - Found303 - See Other304 - Not Modified305 - Use Proxy306 - (Reserved)307 - Temporary Redirect 4xx - C