Http Error Codes 5xx
Server Monitoring Website Monitoring Application Monitoring In-browser monitoring Email System Monitoring with Round-Trip PricesInstant Price QuoteSaved QuotesHow it worksDemo AccountScreenshotsFeaturesMonitoringError detection and verificationAlert NotificationsReportsAccount AdministrationSupportPricingTest Alert ConsoleMonitoring networkLatest FeaturesWhy monitoringWhy WebSitePulseDo the MathMobile AccessSmartPhone InterfaceWAP Interfacelog inForgotten passwordForgotten usernameSign upDemo Accountsign uphelpKnowledge BaseFAQGlossaryContactFeedbackfree toolsTest Tools Website Website Test Web Page Test HTTP Headers Test Link Check China 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 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 V
response. 10.1 Informational 1xx 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. There are no required headers for this class of status code. Since 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. A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the http://www.websitepulse.com/kb/5xx_http_status_codes.html 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 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 https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) 10.1.1 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. 10.1.2 101 Switching Protocols The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response. The protocol SHOULD be switched only when it is advantageous to do so. For example, switchin
1xx: Informational - Request received, continuing process 2xx: Success - The action was successfully received, understood, and accepted 3xx: Redirection - Further action must be taken in order http://www.iana.org/assignments/http-status-codes to complete the request 4xx: Client Error - The request contains https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-http-error-codes bad syntax or cannot be fulfilled 5xx: Server Error - The server failed to fulfill an apparently valid request Available Formats CSV Value Description Reference 100 Continue [RFC7231, Section 6.2.1] 101 Switching Protocols [RFC7231, Section 6.2.2] 102 Processing [RFC2518] 103-199 Unassigned 200 OK [RFC7231, Section 6.3.1] 201 http error Created [RFC7231, Section 6.3.2] 202 Accepted [RFC7231, Section 6.3.3] 203 Non-Authoritative Information [RFC7231, Section 6.3.4] 204 No Content [RFC7231, Section 6.3.5] 205 Reset Content [RFC7231, Section 6.3.6] 206 Partial Content [RFC7233, Section 4.1] 207 Multi-Status [RFC4918] 208 Already Reported [RFC5842] 209-225 Unassigned 226 IM Used [RFC3229] 227-299 Unassigned 300 Multiple Choices [RFC7231, Section 6.4.1] 301 Moved Permanently [RFC7231, Section http error codes 6.4.2] 302 Found [RFC7231, Section 6.4.3] 303 See Other [RFC7231, Section 6.4.4] 304 Not Modified [RFC7232, Section 4.1] 305 Use Proxy [RFC7231, Section 6.4.5] 306 (Unused) [RFC7231, Section 6.4.6] 307 Temporary Redirect [RFC7231, Section 6.4.7] 308 Permanent Redirect [RFC7538] 309-399 Unassigned 400 Bad Request [RFC7231, Section 6.5.1] 401 Unauthorized [RFC7235, Section 3.1] 402 Payment Required [RFC7231, Section 6.5.2] 403 Forbidden [RFC7231, Section 6.5.3] 404 Not Found [RFC7231, Section 6.5.4] 405 Method Not Allowed [RFC7231, Section 6.5.5] 406 Not Acceptable [RFC7231, Section 6.5.6] 407 Proxy Authentication Required [RFC7235, Section 3.2] 408 Request Timeout [RFC7231, Section 6.5.7] 409 Conflict [RFC7231, Section 6.5.8] 410 Gone [RFC7231, Section 6.5.9] 411 Length Required [RFC7231, Section 6.5.10] 412 Precondition Failed [RFC7232, Section 4.2] 413 Payload Too Large [RFC7231, Section 6.5.11] 414 URI Too Long [RFC7231, Section 6.5.12] 415 Unsupported Media Type [RFC7231, Section 6.5.13][RFC7694, Section 3] 416 Range Not Satisfiable [RFC7233, Section 4.4] 417 Expectation Failed [RFC7231, Section 6.5.14] 418-420 Unassigned 421 Misdirected Request [RFC7540, Section 9.1.2] 422 Unprocessable Entity [RFC4918] 423 Locked [RFC4918] 424 Failed Dependency [RFC4918] 425 Unas
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.4k 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 i