Custom Http Error Messages
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 Transfer Protocol (HTTP) response status custom error messages rails codes. It includes codes from IETF internet standards, other IETF RFCs, other specifications, and
Grails Custom Error Messages
some additional commonly used codes. The first digit of the status code specifies one of five classes of response; an HTTP client show friendly http error messages 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, the status code is part of the HTTP/1.1 standard (RFC
Custom Http Error Pages
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 code). Contents 1 1xx Informational 2 2xx Success 3 3xx Redirection 4 4xx Client Error 5 custom http error codes 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 not be continued.[2] 101 Switching Protocols The requester has asked the server to switch protocols and the server has agreed to do so.[5] 102 Processing (WebDAV; RFC 2518) A WebDAV request may
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs
Http Error Codes Cheat Sheet
and reference Dev centers Retired content Samples We’re sorry. The content you
Http Error Codes 403
requested has been removed. You’ll be auto redirected in 1 second. Internet Information Services (IIS) 6.0 SDK IIS http error codes 404 Programmatic Administration SDK IIS Programmatic Administration Reference IIS Programmatic Administration Reference IIS Custom HTTP Error Messages IIS Custom HTTP Error Messages IIS Custom HTTP Error Messages IIS Metabase Properties https://en.wikipedia.org/wiki/List_of_HTTP_status_codes IIS Scripting API for Programmatic Administration IIS COM API for Programmatic Administration IIS Custom HTTP Error Messages IIS Events and Error Messages IIS Internet Database Connector Reference IIS Logging Properties IIS Performance Counters IIS Registry Entries TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived https://msdn.microsoft.com/en-us/library/ms525983(v=vs.90).aspx and is not being maintained. IIS Custom HTTP Error Messages IIS 6.0 When a client makes an invalid request to an IIS server, IIS responds with an error code that is congruent with the HTTP 1.1 specification. IIS comes with a set of HTTP 1.1 error files in HTML format. However, IIS can be configured to send alternative files or strings. For information about how to configure IIS to send alternative error files, see the topics Configuring Custom Error Messages and Substatus Error Codes in Log Files on the Microsoft TechNet Web site. Additional information can be found in Best Practices with Custom Error Pages.HTTP 1.1 Error MessagesHTTP 1.1 error messages are returned to the client browser in the form of an HTML page that contains a generic message. When a user attempts to connect to a Web site and an HTTP error occurs, an error message is sent back to the client browser with a brief description of what happened during the attempt to establish a connection. For example, if a user attempts to connect to
generic error responses in the event of 4xx or 5xx HTTP status codes, these responses are rather stark, uninformative, https://httpd.apache.org/docs/2.4/custom-error.html and can be intimidating to site users. You may wish to provide custom error responses which are either friendlier, or in some language other than English, or perhaps which are styled http://programmers.stackexchange.com/questions/218080/should-i-make-up-my-own-http-status-codes-a-la-twitter-420-enhance-your-calm more in line with your site layout. Customized error responses can be defined for any HTTP status code designated as an error condition - that is, any 4xx or 5xx status. http error Additionally, a set of values are provided, so that the error document can be customized further based on the values of these variables, using Server Side Includes. Or, you can have error conditions handled by a cgi program, or other dynamic handler (PHP, mod_perl, etc) which makes use of these variables. Configuration Available Variables Customizing Error Responses Multi Language Custom Error Documents http error codes See alsoComments Configuration Custom error documents are configured using the ErrorDocument directive, which may be used in global, virtualhost, or directory context. It may be used in .htaccess files if AllowOverride is set to FileInfo. ErrorDocument 500 "Sorry, our script crashed. Oh dear" ErrorDocument 500 /cgi-bin/crash-recover ErrorDocument 500 http://error.example.com/server_error.html ErrorDocument 404 /errors/not_found.html ErrorDocument 401 /subscription/how_to_subscribe.html The syntax of the ErrorDocument directive is: ErrorDocument <3-digit-code>
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Programmers Questions Tags Users Badges Unanswered Ask Question _ Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Should I make up my own HTTP status codes? (a la Twitter 420: Enhance Your Calm) up vote 16 down vote favorite 2 I'm currently implementing an HTTP API, my first ever. I've been spending a lot of time looking at the Wikipedia page for HTTP status codes, because I'm determined to implement the right codes for the right situations. Listed on that page is a code with number 420, which is a custom code that Twitter used to use for rate limiting. There is already a code for rate limiting, though. It's 429. This led me to wonder why they would set a custom one, when there is already a use case. Is that just being cute? And if so, then which circumstances would make it acceptable to return a different status code, and what, if any problems may clients have with it? I read somewhere that Mozilla doesn't implement the joke 418: I’m a teapot response, which makes me think that clients choose which status codes they implement. If that's true, then I can imagine Twitter's funny little enhance your calm code being problematic. Unless I'm mistaken, and we can appropriate any code number to mean whatever we like, and that only convention dictates that 404 means not found, and 429 means take it easy. api-design http share|improve this question edited Nov 11 '13 at 3:15 Michael Hampton 2,1431915 asked Nov 10 '13 at 23:47 Max Bucknell 18815 migrated from serverfault.com Nov 11 '13 at 0:33 This question came from our site for system and network administrators. add a comment| 2 Answers 2 active oldest votes up vote 25 down vote accepted The whole of the Internet is built on conventions. We call them RFCs. While nobody will come and arrest you if you violate an RFC, you do run the risk that your service will not interoperate with the rest of the wor