Retrieved 16 October 2015. ^ Delta encoding in HTTP. x /apis/sms-mms /apis/mms/docs The Device Capabilities API was deprecated on July 29, 2015. Retrieved 16 October 2015. ^ "407". It is non-committal, meaning that there is no way in HTTP to later send an asynchronous response indicating the outcome of processing the request. this contact form
This response is only cacheable if indicated by a Cache-Control or Expires header field. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format. 416 Requested Range Not Satisfiable A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.) When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource (see section 14.16). Unexpected 1xx status responses MAY be ignored by a user agent. Wikipedia The server either does not recognise the request method, or it lacks the ability to fulfill the request. 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. https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-http-error-codes
The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. Client error responses 400 Bad Request This response means that server could not understand the request due to invalid syntax. 401 Unauthorized Authentication is needed to get requested response. This is similar to 403, but in this case, authentication is possible. 402 Payment Required This response code is reserved for future use.
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. Stack Overflow. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. Http 500 It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes.
The server MUST send a final response after the request has been completed. Http Error Wordpress The server returns no information to the client and closes the connection (useful as a deterrent for malware). 449 Retry With (Microsoft) Wikipedia A Microsoft extension. Retrieved November 11, 2015. ^ Sigler, Chris. "416 Requested Range Not Satisfiable". HTTP, FTP, LDAP) or some other auxiliary server (e.g.
Since HTTP/1.1 304 Not Modified If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. Http Response Example The entity returned with this response SHOULD include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled. 10.2.4 203 Non-Authoritative Information The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. User agents SHOULD display any included entity to the user. The client MAY repeat the request with a suitable Proxy-Authorization header field (section 14.34).
The protocol SHOULD be switched only when it is advantageous to do so. http://www.restapitutorial.com/httpstatuscodes.html Typically, this means that the other permissions of the file should be set to read. Http Status Codes Cheat Sheet The server MAY close the connection to prevent the client from continuing the request. Http Code 403 It is a very rare error and generally requires that the web server be updated. 502 Bad Gateway This error is usually due to improperly configured proxy servers.
It can be used both when the set of request header fields in total are too large, and when a single header field is at fault. http://orgias.org/http-code/html-web-error-codes.html By requiring requests to be conditional, the server can assure that clients are working with the correct copies. If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional. 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. Http Code 302
About AT&T Sponsored Data x /sponsored-data-tutorials /sponsored-data-tutorials/getting-started /sponsored-data-tutorials/manifest /sponsored-data-tutorials/mechanics /sponsored-data-tutorials/manifest-errors /sponsored-data-tutorials/certificate /sponsored-data-tutorials/install-certificate /sponsored-data-tutorials/portal /sponsored-data-tutorials/csr /sponsored-data-tutorials/dns /sponsored-data-tutorials/onboarding /sponsored-data-tutorials/docs /sponsored-data-tutorials/faq /sponsored-data-tutorials/simulator/video-1 /sponsored-data-tutorials/simulator/video-2 /sponsored-data-tutorials/simulator/video-3 /sponsored-data-tutorials/simulator/video-4 /sponsored-data-tutorials/simulator/video-5 /sponsored-data-tutorials/simulator/video-6 /sponsored-data-tutorials/simulator/video-7 /sponsored-data-tutorials/simulator/video-8 /sponsored-data-tutorials/simulator/video-9 /sponsored-data-tutorials/simulator/ineligible-1 /sponsored-data-tutorials/simulator/ineligible-2 /sponsored-data-tutorials/simulator/ineligible-3 /sponsored-data-tutorials/simulator/ineligible-4 /sponsored-data-tutorials/simulator/ineligible-5 /sponsored-data-tutorials/simulator/ineligible-6 /sponsored-data-tutorials/simulator/ineligible-7 /sponsored-data-tutorials/simulator/ineligible-8 /sponsored-data-tutorials/simulator/ineligible-9 /sponsored-data-tutorials/examples /sponsored-data-tutorials/examples/tunnel /sponsored-data-tutorials/examples/video-download /sponsored-data-tutorials/examples/cdn /sponsored-data-tutorials/examples/ssl /sponsored-data-tutorials/examples/chunked /sponsored-data-tutorials/examples/management /sponsored-data-tutorials/examples/upload Site Optimized for Chrome and Firefox Site Optimized for Chrome and Firefox Site Optimized for Chrome and Firefox Site Optimized for Chrome and Firefox Site Optimized for Chrome and Firefox The MMS API was deprecated on July 29, 2015. Retrieved January 8, 2015. ^ "401". 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. http://orgias.org/http-code/html-error-codes-400.html Wikipedia The server detected an infinite loop while processing the request (sent in lieu of 208). 509 Bandwidth Limit Exceeded (Apache) Wikipedia This status code, while used by many servers, is not specified in any RFCs. 510 Not Extended The policy for accessing the resource has not been met in the request.
The entity format is specified by the media type given in the Content-Type header field. Http 422 Intended to prevent "the "lost update" problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict. 429 Too Many Requests The 429 status code indicates that the user has sent too many requests in a given amount of time ("rate limiting"). REST Quick Tips HTTP Methods Resource Naming Idempotence HTTP Status Codes Resources Hypertext Transfer Protocol (HTTP) Status Code Registry Last Updated 2016-03-01 Available Formats XML HTML Plain text Registry included below HTTP Status Codes HTTP Status Codes Registration Procedure(s) IETF Review Reference [RFC7231] Note 1xx: Informational - Request received, continuing process 2xx: Success - The action was successfully received, understood, and accepted 3xx: Redirection - Further action must be taken in order to complete the request 4xx: Client Error - The request contains bad syntax or cannot be fulfilled 5xx: Server Error - The server failed to fulfill an apparently valid request Available Formats CSV Value Description Reference 100 Continue [RFC7231, Section 6.2.1] 101 Switching Protocols [RFC7231, Section 6.2.2] 102 Processing [RFC2518] 103-199 Unassigned 200 OK [RFC7231, Section 6.3.1] 201 Created [RFC7231, Section 6.3.2] 202 Accepted [RFC7231, Section 6.3.3] 203 Non-Authoritative Information [RFC7231, Section 6.3.4] 204 No Content [RFC7231, Section 6.3.5] 205 Reset Content [RFC7231, Section 6.3.6] 206 Partial Content [RFC7233, Section 4.1] 207 Multi-Status [RFC4918] 208 Already Reported [RFC5842] 209-225 Unassigned 226 IM Used [RFC3229] 227-299 Unassigned 300 Multiple Choices [RFC7231, Section 6.4.1] 301 Moved Permanently [RFC7231, Section 6.4.2] 302 Found [RFC7231, Section 6.4.3] 303 See Other [RFC7231, Section 6.4.4] 304 Not Modified [RFC7232, Section 4.1] 305 Use Proxy [RFC7231, Section 6.4.5] 306 (Unused) [RFC7231, Section 6.4.6] 307 Temporary Redirect [RFC7231, Section 6.4.7] 308 Permanent Redirect [RFC7538] 309-399 Unassigned 400 Bad Request [RFC7231, Section 6.5.1] 401 Unauthorized [RFC7235, Section 3.1] 402 Payment Required [RFC7231, Section 6.5.2] 403 Forbidden [RFC7231, Section 6.5.3] 404 Not Found [RFC7231, Section 6.5.4] 405 Method Not Allowed [RFC7231, Section 6.5.5] 406 Not Acceptable [RFC7231, Section 6.5.6] 407 Proxy Authentication Required [RFC7235, Section 3.2] 408 Request Timeout [RFC7231, Section 6.5.7] 409 Conflict [RFC7231, Section 6.5.8] 410 Gone [RFC7231, Section 6.5.9] 411 Length Required [RFC7231, Section 6.5.10] 412 Precondition Failed [RFC7232, Section 4.2] 413 Payload Too Large [RFC7231, Section 6.5.11] 414 URI Too Long [RFC7231, Section 6.5.12] 415 Unsupported Media Type [RFC7231, Section 6.5.13][RFC7694, Section 3] 416 Range Not Satisfiable [RFC7233, Section 4.4] 417 Expectation Failed [RFC7231, Section 6.5.14] 418-420 Unassigned 421 Misdirected Request [RFC7540, Section 9.1.2] 422 Unprocessable Entity [RFC4918] 423 Locked [RFC4918] 424 Failed Dependency [RFC4918] 425 Unassigned 426 Upgrade Required [RFC7231, Section 6.5.15] 427 Unassigned 428 Precondition Required [RFC6585] 429 Too Many Requests [RFC6585] 430 Unassigned 431 Request Header Fields Too Large [RFC6585] 432-450 Unassigned 451 Unavailable For Legal Reasons [RFC7725] 452-499 Unassigned 500 Internal Server Error [RFC7231, Section 6.6.1] 501 Not Implemented [RFC7231, Section 6.6.2] 502 Bad Gateway [RFC7231, Section 6.6.3] 503 Service Unavailable [RFC7231, Section 6.6.4] 504 Gateway Timeout [RFC7231, Section 6.6.5] 505 HTTP Version Not Supported [RFC7231, Section 6.6.6] 506 Variant Also Negotiates [RFC2295] 507 Insufficient Storage [RFC4918] 508 Loop Detected [RFC5842] 509 Unassigned 510 Not Extended [RFC2774] 511 Network Authentication Required [RFC6585] 512-599 Unassigned Contents Share Twitter Facebook Google+ Hacker News Share Twitter Facebook Google+ Hacker News × Sign up for our newsletter.
In the latter case, the response representation SHOULD specify which header field was too large. Note that the 511 response SHOULD NOT contain a challenge or the login interface itself, because browsers would show the login interface as being associated with the originally requested URL, which may cause confusion. There are several ways to ensure this, but the following command will work in this case: sudo chmod o=r /usr/share/nginx/html/index.html .htaccess Another potential cause of 403 errors, often intentinally, is the use of an .htaccess file. Http 404 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).
Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. A first digit of 4 represents a client—side error, with the most common codes in the range of 400 to 404. Retrieved 16 October 2015. ^ "RFC2616 on status 414". http://orgias.org/http-code/html-error-codes-200.html Retrieved 2016-01-09. ^ "ngx_http_special_response.c".
Retrieved 16 October 2015. ^ "HTTP Error 504 Gateway timeout". The bare minimum for an HTTP client is that it recognizes these five classes. Likewise, user agents should display any included entity to the user. However, the problem may also arise when there is poor IP communication between back—end computers, when the client's server is overloaded, or when a firewall is functioning improperly.
The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The response representation SHOULD contain a link to a resource that allows the user to submit credentials (e.g. 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. 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.
httpstatus. It's important to be aware of what the HTTP 400 and 500 Error Codes mean so that you can address the issues that they raise, especially if you have control over the cause. 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. It is intended for cases where another process or server handles the request, or for batch processing. 203 Non-Authoritative Information This response code means returned meta-information set is not exact set as available from the origin server, but collected from a local or a third party copy.
Does the user that owns the web server worker process have privileges to traverse to the directory that the requested file is in? (Hint: directories require read and execute permissions to be accessed) Is the resource being accessed a symbolic link? Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. The client MAY repeat the request without modifications at any later time." 409 Conflict Indicates that the request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates. 410 Gone Indicates that the resource requested is no longer available and will not be available again. Retrieved February 4, 2015. ^ "List of HTTP status codes".
Retrieved November 11, 2015. ^ TheDeadLike. "HTTP/1.1 Status Codes 400 and 417, cannot choose which". Stack Overflow.