300 Http Error Codes
Contents |
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 http statuses status code. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT
Response Codes List
send a 1xx response to an HTTP/1.0 client except under experimental conditions. A client MUST be prepared to accept one or more http error codes cheat sheet 1xx status responses prior to a regular 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, http error codes 403 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 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
Http Error Codes 404
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, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features. 10.2 Successful 2xx This class of status code indicates that the client's request was successfully received, understood, and accepted. 10.2.1 200 OK The request has succeeded. The information returned with the response is dependent on the method used in the request, for example: GET an entity
account: GitHub Sign in: Persona Web Platform Technologies HTML CSS JavaScript Graphics HTTP APIs / DOM Apps MathML References common http error codes & Guides Learn the Web Tutorials References Developer Guides Accessibility custom http error codes Game development ...more docs Mozilla Docs Add-ons Firefox WebExtensions Developer ToolsFeedback Get Firefox help Get
Http Error Code 302
web development help Join the MDN community Report a content problem Report a bug Search Search Languages 日本語 (ja) 한국어 (ko) Русский (ru) https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html 中文 (简体) (zh-CN) 正體中文 (繁體) (zh-TW) Add a translation Edit Advanced Advanced History Print this article MDN Web technology For developers HTTP HTTP response status codes Your Search Results fscholz sivasain arulnithi rctgamer3 groovecoder dovgart Sheppy fusionchess HTTP response status codes In This Article Information responsesSuccessful responsesRedirection messagesClient https://developer.mozilla.org/en-US/docs/Web/HTTP/Status error responsesServer error responses HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes: informational responses, successful responses, redirects, client errors, and servers errors. Information responses 100 Continue This interim response indicates that everything so far is OK and that the client should continue with the request or ignore it if it is already finished. 101 Switching Protocol This code is sent in response to an Upgrade: request header by the client, and indicates that the protocol the server is switching too. It was introduced to allow migration to an incompatible protocol version, and is not in common use. Successful responses 200 OK The request has succeeded. The meaning of a success varies depending on the HTTP method: GET: The resource has been fetched and is transmitted in the message body. HEAD: The entity
1xx: Informational - Request received, continuing process 2xx: Success - The action was successfully received, understood, and accepted 3xx: Redirection - Further action http://www.iana.org/assignments/http-status-codes must be taken in order to complete the request 4xx: Client http://www.websitepulse.com/kb/3xx_http_status_codes.html Error - The request contains 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] http error 103-199 Unassigned 200 OK [RFC7231, Section 6.3.1] 201 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] http error code 227-299 Unassigned 300 Multiple Choices [RFC7231, Section 6.4.1] 301 Moved Permanently [RFC7231, Section 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 E
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 Day2