Apache Http Error Codes
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
Apache Http Response Codes
Protocol (HTTP) response status codes. It includes codes from IETF internet standards, other apache error 302 IETF RFCs, other specifications, and some additional commonly used codes. The first digit of the status code specifies one of
Http Error Codes Cheat Sheet
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, the http error codes 403 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 code). Contents http error codes 404 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 not be continued.[2] 101 Switc
In submit Tutorials Questions Projects Meetups Main Site logo-horizontal DigitalOcean Community Menu Tutorials Questions Projects Meetups Main Site Sign Up Log In submit View All Results By: Mitchell Anicas Subscribe Subscribed Share Contents Contents We hope you find this tutorial helpful. In addition
Common Http Error Codes
to guides like this one, we provide simple cloud infrastructure for developers. Learn more → 10 custom http error codes How To Troubleshoot Common HTTP Error Codes Posted Oct 24, 2014 77.9k views FAQ Apache Nginx Introduction When accessing a web server or application,
Http Error Code 500
every HTTP request that is received by a server is responded to with an HTTP status code. HTTP status codes are three-digit codes, and are grouped into five different classes. The class of a status code can be quickly identified https://en.wikipedia.org/wiki/List_of_HTTP_status_codes by its first digit: 1xx: Informational 2xx: Success 3xx: Redirection 4xx: Client Error 5xx: Server Error This guide focuses on identifying and troubleshooting the most commonly encountered HTTP error codes, i.e. 4xx and 5xx status codes, from a system administrator's perspective. There are many situations that could cause a web server to respond to a request with a particular error code--we will cover common potential causes and solutions. Client and Server Error Overview Client errors, or HTTP status codes from https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-http-error-codes 400 to 499, are the result of HTTP requests sent by a user client (i.e. a web browser or other HTTP client). Even though these types of errors are client-related, it is often useful to know which error code a user is encountering to determine if the potential issue can be fixed by server configuration. Server errors, or HTTP status codes from 500 to 599, are returned by a web server when it is aware that an error has occurred or is otherwise not able to process the request. General Troubleshooting Tips When using a web browser to test a web server, refresh the browser after making server changes Check server logs for more details about how the server is handling the requests. For example, web servers such as Apache or Nginx produce two files called access.log and error.log that can be scanned for relevant information Keep in mind that HTTP status code definitions are part of a standard that is implemented by the application that is serving requests. This means that the actual status code that is returned depends on how the server software handles a particular error--this guide should generally point you in the right direction Now that you have a high-level understanding of HTTP status codes, we will look at the commonly encountered errors. 400 Bad Request The 400 status code, or Bad Request error, means the HTTP request that was sent to the serve
Name Lookup Recommended Hosting Solutions Free Hosting -The Fun Tutorials- Lots of HTML Tricks and Tutorials HTML http://www.bignosebird.com/apache/a5.shtml Tag Guide JavaScript Tricks and Tutorials Navigation Tricks Image Maps Tutorial -CGI, SSI and Unix Tutorials- SSI: Server Side Includes Forms Tutorial CGI Simple Tutorial Your First CGI Perl Script Banner Rotation Squawk: Recent News UNIX Guru Tutorial -Web Page Design Tutorials- Design Basics Most Important Part of your Page Photo Composition Tutorials MIDI http error 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 the Secure Server How to Promote Your Web Site Site Management Site Security Password Protection on Directories Site Diagnostics Script Troubleshooting -Resource Links- Offsite http error code 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 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