Http 3xx 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 Protocol
Http Status Code
(HTTP) response status codes. It includes codes from IETF internet standards, other IETF http status codes cheat sheet RFCs, other specifications, and some additional commonly used codes. The first digit of the status code specifies one of five classes http code 403 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 status code
Http Response Example
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 1 1xx Informational
Http Code 302
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 Switching Protocols The requester has asked
Server Monitoring Website Monitoring Application Monitoring In-browser monitoring Email http 422 System Monitoring with Round-Trip PricesInstant Price QuoteSaved QuotesHow it
Http 502
worksDemo AccountScreenshotsFeaturesMonitoringError detection and verificationAlert NotificationsReportsAccount AdministrationSupportPricingTest Alert ConsoleMonitoring networkLatest FeaturesWhy monitoringWhy WebSitePulseDo the MathMobile http 504 AccessSmartPhone InterfaceWAP Interfacelog inForgotten passwordForgotten usernameSign upDemo Accountsign uphelpKnowledge BaseFAQGlossaryContactFeedbackfree toolsTest Tools Website Website Test Web Page Test HTTP Headers Test Link Check China https://en.wikipedia.org/wiki/List_of_HTTP_status_codes Firewall Test DNS HostName Lookup MX Records Lookup NS Records Lookup SPF Lookup Reverse DNS Blacklist Check Service Server Test Email Validation Port Scan Network PING Traceroute TCP Traceroute WHOIS IP / Network Lookup MTR - Tracert & Ping For Your WebsiteGoogle GadgetsAccount StatusAll-In-OneWebsite TestWeb Page TestServer TestHostNamePINGWHOISTracerouteHTTP http://www.websitepulse.com/kb/3xx_http_status_codes.html HeadersChina FirewallMX LookupNS Records LookupSPF LookupReverse DNSEmail ValidationIP/Network LookupMTR - Traceroute & PingBlacklist CheckFirefox ExtensionsCurrent StatusTransaction RecorderTest ToolsSite RecorderIE Add-onsCurrent StatusChrome ExtensionCurrent StatusTest ToolsTransaction RecorderOpera ExtensionCurrent StatusTest ToolsSafari ExtensionCurrent StatusTest ToolsWindows GadgetCurrent StatusFacebook AppsCurrent StatusTest ToolsAndroid AppiPhone & iPad Appabout usAbout UsFrom the Desk of CEOManagementMission StatementAnnual OverviewContactFeedbackServicesWhy WebSitePulseWho uses usMonitoring NetworkLatest FeaturesFeedbackOur clientsTestimonialsCase StudiesWho Uses UsPress RoomLatest NewsPress ReleasesIn the NewsCompany LogosNewslettersArticlesFactsheetCareersSenior Sales ExecutiveSales RepresentativesPoliciesBilling PolicyPrivacy PolicyTerms & ConditionsService AgreementBlogButtonsPerformance Tracking2016 Hurricane Season2016 Vacation Planning2016 Mother's Day2016 Tax Websites2016 Valentine's Day2015 Holiday Season2015 Hurricane Season2015 Vacation Planning2015 Mother's Day2015 Tax Websites2015 Valentine's Day2014 Holiday Season2014 Hurricane Season2014 Vacation Planning2014 Mother's Day2014 Tax Websites2014 Valentine's Day2013 Holiday Season2013 Hurricane Season2013 Vacation Planning2013 Mother's Day2013 Tax Websites2013 Valentine's Day2012 Holiday Season2012 Hurricane Season2012 Vacation Planning2012 Mother's Day2012 Tax Websites2012 Valentine's Day2011 Holiday Season2011 Hurricane Season2011 Vacation Planning2011 Mother's DayPerformance Reports ArchiveCustom ReportscontactContactFeedbackAffiliates HelpKnowledg
consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any http://www.restapitutorial.com/httpstatuscodes.html 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a regular https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-http-error-codes response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx responses, unless the connection between the proxy and http status its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) Wikipedia 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 status code 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. 100 Continue The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code. Wikipedia This means that the server has received the request headers, and that 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). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect: 100-continue as a header in its initial request and check if a 100 Continue status
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 to guides like this one, we provide simple cloud infrastructure for developers. Learn more → 10 How To Troubleshoot Common HTTP Error Codes Posted Oct 24, 2014 82.8k views FAQ Apache Nginx Introduction When accessing a web server or application, 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 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 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 server