Http Error Code 602
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
Http Status Code 400
Protocol (HTTP) response status codes. It includes codes from IETF internet standards, other http code 403 IETF RFCs, other specifications, and some additional commonly used codes. The first digit of the status code specifies one of
Http Code 302
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 504 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 503 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 Swit
SEO with marketing resources for all skill levels: best practices, industry
Http 502
survey results, webinarsandmore. Advance your marketing skills: Local http response example Marketing | Content | Social Media Get started with: The Beginner's Guide to
Http 422
SEO The Local Learning Center The Beginner's Guide to ContentMarketing Q&A Get answers from the Moz Community Help Hub Learn https://en.wikipedia.org/wiki/List_of_HTTP_status_codes how to use Moz Products Community & Events Connect with 500K online marketers Blogs Read the Moz Blog and YouMoz Help Hub Moz Help Moz Updates Moz Health Contact Help Moz HelpGetting StartedOverviewGetting Started ChecklistCampaign SetupCampaign SettingsYour AccountYour Moz HomepageWorkshops https://moz.com/help/guides/moz-pro-overview/crawl-diagnostics/errors-in-crawl-reports & TrainingMoz Pro HelpOverviewDashboardKeyword RankingsAnalyze a KeywordAdd and Manage KeywordsSERP FeaturesLanding PagesPage OptimizationSite CrawlAnalyze Page IssuesErrors in Crawl ReportsLinksLink AnalysisOpportunities Competitive MetricsTraffic From SearchSocialFacebookTwitterGoogle+Most Engaging Posts and TweetsCustom ReportsResearch Tools HelpOverviewOpen Site ExplorerInbound LinksJust-Discovered LinksTop PagesLinking DomainsAnchor TextCompare Link MetricsSpam AnalysisLink OpportunitiesAdvanced ReportsHTTPS CrawlingMozscape Link Index UpdatesFresh Web ExplorerKeyword DifficultyOn-page GraderCrawl TestRank TrackerMozBarKeyword ExplorerOverviewRank CheckingFollowerwonk HelpOverviewSearch BiosCompare UsersAnalyzeTrack FollowersSort FollowersMoz Local HelpOverviewPurchase a ListingDashboardMoz Local InsightsCheck a ListingMy Business ConsoleMoz Content HelpMoz API HelpOverviewMozscape APIOverviewFree vs Paid Access to the Mozscape APIHow to Attribute Mozscape API DataGetting Started with MozscapeCreate and Manage Your AccountAnatomy of a Mozscape API CallSigned AuthenticationBest PracticesSpam ScoreAPI ReferenceAnchor Text MetricsLink MetricsTop Pages MetricsURL MetricsIndex MetadataCommon Query ParametersAPI Call Response FieldsHTTP Status CodesSample Code on Gi
Friendly Test » Keyword Density » Keyword Generator » MozRank Checker » Alexa Ranking » PageRank Check » Twitter Card Generator » Facebook Open Graph » Social Media Shares » Keyword Analyzer Online Tools » QR Code Generator » IP Geolocation » http://www.seocentro.com/articles/apache/http-status-codes.html My IP Address » Server Headers Check » Share Link Generator » Minify JavaScript » Minify CSS » HTML Encoder » URL Encoder HTTP Status and Error Codes Explained The following is a list of HTTP https://www.mapquestapi.com/directions/status_codes.html response status codes and standard associated phrases, intended to give a short textual description of the status. 1xx Informational 2xx Success 3xx Redirection 4xx Client Error 5xx Server Error 1xx InformationalRequest received, continuing process. top Code http code Status Explanation 100 Continue The request has been completed and the rest of the process can continue. 101 Switching Protocols When requesting a page, a browser might receive a statis code of 101, followed by an "Upgrade" header showing that the server is changing to a different version of HTTP. 2xx SuccessThe action was successfully received, understood, and accepted. top Code Status Explanation 200 OK Standard response for HTTP successful requests. 201 Created http error code When new pages are created by posted form data or by a CGI process, this is confirmation that it worked. 202 Accepted The client's request was accepted, though not yet processed. 203 Non-Authorative Information The information contained in the entity header is not from the original site, but from a third party server. 204 No Content If you click a link which has no target URL, this response is elicited by the server. It's silent and doesn't warn the user about anything. 205 Reset Content This allows the server to reset any content returned by a CGI. 206 Partial Content The requested file wasn't downloaded entirely. This is returned when the user presses the stop button before a page is loaded, for example. 3xx RedirectionThe client must take additional action to complete the request. top Code Status Explanation 300 Multiple Choices The requested address refers to more than one file. Depending on how the server is configured, you get an error or a choice of which page you want. 301 Moved Permanently If the server is set up properly it will automatically redirect the reader to the new location of the file. 302 Moved Temporarily Page has been moved temporarily, and the new URL is available. You should be sent there by the server. 3
Maps Plugin Geocoding Plugin Routing Plugin Traffic Plugin Directions Service: Status Codes/Functional Maximums The following tables describe the error messages that can be returned from an unsuccessful route request. Each function section also lists any functional maximums acceptable for that call. Directions Service Call Status Code Description 0 A successful route call. 400 Invalid Request. 401 Invalid Options. 402 Invalid Location. 403 Key-related error. 500 Unknown error. 600 Invalid session ID. 601 Session ID expired 602 Baseline failed. 604 Exceeded maximum search time. 605 Exceeded maximum search distance. 606 Exceeded maximum number of locations. 607 Failed to get density for all locations. 608 Exceeded pedestrian maximum gross distance for locations. 609 Exceeded maximum gross distance for locations. 610 Ambiguities detected in locations. 611 At least two locations required 612 No routes available for location. Route/Optimized Route Call Status Code Description 601Invalid location specified. 602The route failed, normally due to mustAvoidLinkIds options being set in a way that makes the route impossible. 603No dataset found to calculate the route. 610Ambiguities were found in one or more of the locations specified and ambiguities=ignore was not set. Maximum Description 50Number of locations acceptable. Route Matrix Call Status Code Description 601Invalid location specified. 602The route failed, normally due to mustAvoidLinkIds options being set in a way that makes the route impossible. 603No dataset found to calculate the route. 604Invalid option was specified. 605Partial Success. 606Exceeded maximum locations. Maximum Description 25Number of locations acceptable. Drag Route Call Status Code Description 601Invalid location specified. 602The route failed, normally due to mustAvoidLinkIds options being set in a way that makes the route impossible. 603No dataset found to calculate the route. Maximum Description 20Number of via points acceptable. Route Shape Call Status Code Description 601Invalid session specified. Path from Route Call Status Code Description 601Partial Success 602Exceeded maximum number of POIs 603Not Specified 604Exceeded maximum search time 605Exceeded maximum search distance 606Failure 607No POIs 608No nodes were found within the supplied corridor limits Maximum Description 1000Number of pois. 15 minutesTime to perform search. 10 miles (16 km)Distance to perform search. Products MapQuest.com Mobile Solutions Route Planner Gas Prices Tools & Technology MapQuest Browser Toolbar Developer Network Pla