Http Error 420
Contents |
a reference to this number’s association with marijuana. © Copywrite 2016. From @mikeleeorg.For more goofiness CSS Humor & Web 2.0 Ipsum. Ha ha funny, right? Share with your friends! Tweet
DocumentationBest PracticesAPI OverviewUpcoming changes to TweetsObject: UsersObject: TweetsObject: EntitiesObject: Entities in ObjectsObject: PlacesTwitter IDsConnecting to Twitter API using TLSUsing cursors to navigate collectionsError Codes & ResponsesTwitter LibrariesAPI StatusPlaybooksEventsCase StudiesManage My AppsTerms of UseError Codes & ResponsesHTTP Status CodesThe Twitter API attempts to return appropriate HTTP status codes for every
Http 502
request.CodeTextDescription200OKSuccess!304Not ModifiedThere was no new data to return.400Bad RequestThe request was invalid http response example or cannot be otherwise served. An accompanying error message will explain further. In API v1.1, requests without authentication
Http Error 500 Wordpress
are considered invalid and will yield this response.401UnauthorizedAuthentication credentials were missing or incorrect.Also returned in other circumstances, for example all calls to API v1 endpoints now return 401 (use API https://httpstatusdogs.com/420-enhance-your-calm v1.1 instead).403ForbiddenThe request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why. This code is used when requests are being denied due to update limits. Other reasons for this status being returned are listed alongside the response codes in the table below.404Not FoundThe URI requested is invalid or the resource https://dev.twitter.com/overview/api/response-codes requested, such as a user, does not exists. Also returned when the requested format is not supported by the requested method.406Not AcceptableReturned by the Search API when an invalid format is specified in the request.410GoneThis resource is gone. Used to indicate that an API endpoint has been turned off. For example: "The Twitter REST API v1 will soon stop functioning. Please migrate to API v1.1."420Enhance Your CalmReturned by the version 1 Search and Trends APIs when you are being rate limited.422Unprocessable EntityReturned when an image uploaded to POST account / update_profile_banner is unable to be processed.429Too Many RequestsReturned in API v1.1 when a request cannot be served due to the application's rate limit having been exhausted for the resource. See Rate Limiting in API v1.1.500Internal Server ErrorSomething is broken. Please post to the developer forums so the Twitter team can investigate.502Bad GatewayTwitter is down or being upgraded.503Service UnavailableThe Twitter servers are up, but overloaded with requests. Try again later.504Gateway timeoutThe Twitter servers are up, but the request couldn't be serviced due to some failure within our stack.
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 http://www.restapitutorial.com/httpstatuscodes.html not define any 1xx status codes, servers MUST NOT send a 1xx response to http://programmers.stackexchange.com/questions/218080/should-i-make-up-my-own-http-status-codes-a-la-twitter-420-enhance-your-calm 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 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 http error 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).) Wikipedia Request received, continuing process. This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, http error 420 and is terminated by an empty line. 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. 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 E
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Programmers Questions Tags Users Badges Unanswered Ask Question _ Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Should I make up my own HTTP status codes? (a la Twitter 420: Enhance Your Calm) up vote 16 down vote favorite 2 I'm currently implementing an HTTP API, my first ever. I've been spending a lot of time looking at the Wikipedia page for HTTP status codes, because I'm determined to implement the right codes for the right situations. Listed on that page is a code with number 420, which is a custom code that Twitter used to use for rate limiting. There is already a code for rate limiting, though. It's 429. This led me to wonder why they would set a custom one, when there is already a use case. Is that just being cute? And if so, then which circumstances would make it acceptable to return a different status code, and what, if any problems may clients have with it? I read somewhere that Mozilla doesn't implement the joke 418: I’m a teapot response, which makes me think that clients choose which status codes they implement. If that's true, then I can imagine Twitter's funny little enhance your calm code being problematic. Unless I'm mistaken, and we can appropriate any code number to mean whatever we like, and that only convention dictates that 404 means not found, and 429 means take it easy. api-design http share|improve this question edited Nov 11 '13 at 3:15 Michael Hampton 2,1531915 asked Nov 10 '13 at 23:47 Max Bucknell 18815 migrated from serverfault.com Nov 11 '13 at 0:33 This question came from our site for system and network administrators. add a comment| 2 Answers 2 active oldest votes up vote 25 down vote accepted The whole of the Internet is built on conventions. We call them RFCs. While nobody will come and arrest you if you violate an RFC, you do run the risk that yo