A first digit of 4 represents a client—side error, with the most common codes in the range of 400 to 404. This code indicates that the server has received and is processing the request, but no response is available yet. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. A user agent should detect and intervene to prevent cyclical redirects. 300 Multiple Choices Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation). this contact form
This response is cacheable unless indicated otherwise. 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. 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). List of HTTP status codes From Wikipedia, the free encyclopedia Jump to: navigation, search HTTP Persistence Compression HTTPS Request methods OPTIONS GET HEAD POST PUT DELETE TRACE CONNECT PATCH Header fields Cookie ETag Location HTTP 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 This is a list of Hypertext Transfer Protocol (HTTP) response status codes. User agents SHOULD display any included entity to the user. https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
TRUE will be returned if response_code is provided and it is not invoked in a web server environment (but only when no previous response status has been set). If known, the length of the delay MAY be indicated in a Retry-After header. However, some Web applications and frameworks use the 302 status code as if it were the 303. 303 See Other The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. For example, a POST request should be repeated using another POST request. 308 Permanent Redirect (RFC 7538) The request and all future requests should be repeated using another URI. 307 and 308 parallel the behaviors of 302 and 301, but do not allow the HTTP method to change.
Downloads Documentation Get Involved Help PHP 5.6.27 Released Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Errors Exceptions Generators References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting Using Register Globals User Submitted Data Magic Quotes Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Dealing with XForms Handling file uploads Using remote files Connection handling Persistent Database Connections Safe Mode Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Credit Card Processing Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation Keyboard Shortcuts? Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI. JSEND) are not used and nothing is in the body (e.g. Http Response Example Originally meant "Subsequent requests should use the specified proxy." 307 Temporary Redirect (since HTTP/1.1) In this case, the request should be repeated with another URI; however, future requests should still use the original URI.
If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. Retrieved 16 October 2015. ^ Singh, Prabhat; user1740567. "Spring 3.x JSON status 406 "characteristics not acceptable according to the request "accept" headers ()"". his comment is here Retrieved 16 October 2015. ^ "301".
part of Hypertext Transfer Protocol -- HTTP/1.1 RFC 2616 Fielding, et al. 10 Status Code Definitions Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required in the response. 10.1 Informational 1xx 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. Http 422 Therefore, servers are not required to use the 429 status code; when limiting resource usage, it may be more appropriate to just drop connections, or take other steps. This Best Practice Deep Dive provides some background on what the different classes of HTTP Status Codes represent, describes the issues raised by the most common 400 and 500 Status Codes, and discusses possible resolutions for them. Docs.cpanel.net.
Note: Note to implementors: some deployed proxies are known to return 400 or 500 when DNS lookups time out. 10.5.6 505 HTTP Version Not Supported The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. https://developer.mozilla.org/en-US/docs/Web/HTTP/Status Originally meant "Subsequent requests should use the specified proxy." 307 Temporary Redirect The requested resource resides temporarily under a different URI. Http Status Codes Cheat Sheet However if they know there is a problem with their Web site, they should hopefully tell you so and tell you when they plan to fix the problem. Http Code 403 This should be used when a resource has been intentionally removed and the resource should be purged.
Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s). http://orgias.org/http-code/html-web-error-codes.html This condition is considered to be temporary. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required. Wikipedia The server successfully processed the request, but is not returning any content. Http Code 302
The entity format is specified by the media type given in the Content-Type header field. https://tools.ietf.org/html/rfc2616#section-10.2.1. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. http://orgias.org/http-code/html-error-codes-200.html Bad command or file name Halt and Catch Fire HTTP 418 Out of memory Lists List of HTTP status codes List of FTP server return codes Related Kill screen Spinning pinwheel Windows wait cursor Retrieved from "https://en.wikipedia.org/w/index.php?title=List_of_HTTP_status_codes&oldid=744546936" Categories: Hypertext Transfer Protocol status codesInternet-related listsHidden categories: All articles with unsourced statementsArticles with unsourced statements from July 2016Articles with unsourced statements from August 2016Commons category without a link on WikidataOfficial website missing URLUse mdy dates from November 2012 Navigation menu Personal tools Not logged inTalkContributionsCreate accountLog in Namespaces Article Talk Variants Views Read Edit View history More Search Navigation Main pageContentsFeatured contentCurrent eventsRandom articleDonate to WikipediaWikipedia store Interaction HelpAbout WikipediaCommunity portalRecent changesContact page Tools What links hereRelated changesUpload fileSpecial pagesPermanent linkPage informationWikidata itemCite this page Print/export Create a bookDownload as PDFPrintable version Languages العربيةČeštinaDeutschEspañolفارسیFrançais한국어Bahasa IndonesiaÍslenskaItalianoעבריתქართულიBahasa MelayuNederlands日本語Norsk bokmålPolskiPortuguêsРусскийСрпски / srpskiSvenskaไทยTürkçeУкраїнська中文 Edit links This page was last modified on 15 October 2016, at 23:22.
A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection. Http 404 The error indicates that the server will only temporarily be down. The entity format is specified by the media type given in the Content-Type header field.
These response codes are applicable to any request method. 10.5.1 500 Internal Server Error The server encountered an unexpected condition which prevented it from fulfilling the request. 10.5.2 501 Not Implemented The server does not support the functionality required to fulfill the request. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent's active view. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource. 10.5.3 502 Bad Gateway The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. 10.5.4 503 Service Unavailable The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. Http 502 Unlike a 204 response, this response requires that the requester reset the document view. 206 Partial Content (RFC 7233) The server is delivering only part of the resource (byte serving) due to a range header sent by the client.
W3. httpstatus. Except this condition, 200 OK response should be preferred instead of this response. 204 No Content There is no content to send for this request, but the headers may be useful. his comment is here Retrieved 16 October 2015. ^ "RFC7235 on code 401".
The entity format is specified by the media type given in the Content- Type header field.