Http 501 Error Code
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 This is a list of Hypertext http status code Transfer Protocol (HTTP) response status codes. It includes codes from IETF internet standards,
Http Code 302
other IETF RFCs, other specifications, and some additional commonly used codes. The first digit of the status code specifies one error 501 android of five classes of response; an HTTP client must recognise these five classes at a minimum. The phrases used are the standard wordings, but any human-readable alternative can be provided. Unless otherwise stated, http 403 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 only appear in the response payload and in documentation; not in the place of an actual HTTP status
Http Status Codes Cheat Sheet
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 headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in response before sending the body. The response 417 Expectation Failed indicates the request should n
received when the server does not support the facility http 502 required. Note: A 501 error is not something you can fix, but rather will
Http 422
require a fix by the web server admin who manages the website and server you are trying to access. Web server overload If https://en.wikipedia.org/wiki/List_of_HTTP_status_codes the server you're attempting to load is experiencing high demand it may be unable to complete your request and generate this error. If you're experiencing this error on a known good page, try loading the page again in a few minutes. If that is unsuccessful, http://www.computerhope.com/issues/ch001020.htm try loading the page again later that day or the next day. Web server errors This error can also be encountered when the web server does not properly respond to the web browser's request or the program attempting to make a request with the web server. Web server out of date Finally, in some rare situations, the web server may need a software upgrade to properly communicate with your web browser or program. Additional information See the 501 definition for further information and related links. Was this page useful? YesNo Feedback E-mail Share Print Search Recently added pages View all recent updates Useful links About Computer Hope Site Map Forum Contact Us How to Help Top 10 pages Follow us Facebook Twitter Google+ Pinterest YouTube RSS © 2016 Computer Hope Legal Disclaimer - Privacy Statement
& Guides Learn the Web Tutorials References Developer Guides Accessibility Game development ...more docs Mozilla Docs Add-ons Firefox WebExtensions Developer ToolsFeedback https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/501 Get Firefox help Get web development help Join the MDN community Report a content problem Report a bug Search Search Languages No translations exist for this article. Add a translation Edit Advanced Advanced History Print this article MDN Web technology For developers HTTP HTTP response status codes 501 Not Implemented Your Search Results fscholz Jeremie 501 Not http status Implemented In This Article StatusSpecificationsBrowser compatibility The HTTP 501 Not Implemented server error response code indicates that the request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are GET and HEAD. Note that a 501 error is not something http status code you can fix, but requires a fix by the web server you are trying to access. A 501 response is cacheable by default. Status 501 Not Implemented Specifications Specification Title RFC 7231, section 6.6.2: 501 Not Implemented Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content Browser compatibility The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request. DesktopMobile Feature Chrome Edge Firefox Internet Explorer Opera Safari Servo Basic Support(Yes)(Yes)(Yes)(Yes)(Yes)(Yes)(Yes) Feature Android Chrome for Android Edge Mobile Firefox for Android IE Mobile Opera Mobile Safari Mobile Basic Support(Yes)(Yes)(Yes)(Yes)(Yes)(Yes)(Yes) Document Tags and Contributors Tags: HTTP Server error Status code Contributors to this page: fscholz, Jeremie Last updated by: fscholz, Aug 31, 2016, 4:15:01 AM See also HTTP Guides: Resources and URIs Identifying resources on the Web Data URIs Introduction to MIME Types Complete list of MIME Types Choosing between www and non-www URLs Basics of HTTP Overview of HTTP Evolution of HTTP HTTP Messages A typical HTTP session