Apache Web Server Error Codes
Contents |
referer DNT X-Forwarded-For Status codes 301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451
Apache Web Server Source Code
Unavailable For Legal Reasons v t e This is a list http server error codes of Hypertext Transfer Protocol (HTTP) response status codes. It includes codes from IETF internet standards, other dell server error codes IETF RFCs, other specifications, and some additional commonly used codes. The first digit of the status code specifies one of five classes of response; an HTTP
Windows Server Error Codes
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, 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
Sql Server Error Codes
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 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 reques
Name Lookup Recommended Hosting Solutions Free Hosting -The Fun Tutorials- Lots of HTML Tricks and Tutorials HTML Tag Guide JavaScript Tricks and Tutorials Navigation Tricks Image Maps Tutorial -CGI, SSI and Unix apache error 302 Tutorials- SSI: Server Side Includes Forms Tutorial CGI Simple Tutorial Your First CGI Perl
Web Service Error Codes
Script Banner Rotation Squawk: Recent News UNIX Guru Tutorial -Web Page Design Tutorials- Design Basics Most Important Part of your Page server beep codes Photo Composition Tutorials MIDI Music on Your Pages All about COLOR THE SAFE Colors The Skinny on Fat Graphics Advanced Design Examples ASCII Chart -Managing Your Web Site- BNB on the APACHE Server Introduction to https://en.wikipedia.org/wiki/List_of_HTTP_status_codes the Secure Server How to Promote Your Web Site Site Management Site Security Password Protection on Directories Site Diagnostics Script Troubleshooting -Resource Links- Offsite Resource Links Good Books The Tools You Need -All the Other Stuff- Newletter Back Issues Reader's Links Bird Droppings: Letters Kudos / Awards BNB FAQ Guestbook WARNING: Be very careful editing your server configuration or .htaccess files. Even a minor typographical error can make http://www.bignosebird.com/apache/a5.shtml your site unusable! Always make a backup copy of any file so you can recover quickly. THE APACHE SERVER STATUS & ERROR CODES Successful Client Requests 200 OK 201 Created 202 Accepted 203 Non-Authorative Information 204 No Content 205 Reset Content 206 Partial Content Client Request Redirected 300 Multiple Choices 301 Moved Permanently 302 Moved Temporarily 303 See Other 304 Not Modified 305 Use Proxy Client Request Errors 400 Bad Request 401 Authorization Required 402 Payment Required (not used yet) 403 Forbidden 404 Not Found 405 Method Not Allowed 406 Not Acceptable (encoding) 407 Proxy Authentication Required 408 Request Timed Out 409 Conflicting Request 410 Gone 411 Content Length Required 412 Precondition Failed 413 Request Entity Too Long 414 Request URI Too Long 415 Unsupported Media Type Server Errors 500 Internal Server Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout 505 HTTP Version Not Supported Find or Give Help on the BBS Home Top E-Mail If it looks great, it's by Christine Some Fine Print © 1997-2003 BigNoseBird.Com®, Inc. All rights reserved. All other trademarks are the sole property of their respective owners. The products that we recommend are only ones that we use. We have no relationship with any of
generic error responses in the event of 4xx or 5xx HTTP status codes, these responses are rather stark, uninformative, and can be intimidating to site users. You https://httpd.apache.org/docs/2.4/custom-error.html may wish to provide custom error responses which are either friendlier, or in some language other than English, or perhaps which are styled 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. Additionally, a set of values are provided, so that the error document can be customized further error codes 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 See alsoComments Configuration Custom error documents are configured using the ErrorDocument directive, which may be used in global, virtualhost, or directory context. It server error codes 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>