Rate Limit Http Error
Contents |
tour help Tour Start 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 http error code 429 About Us Learn more about Stack Overflow the company Business Learn more about http 429 retry after hiring developers or posting ads with us Software Engineering Questions Tags Users Badges Unanswered Ask Question _ Software Engineering Stack http rate limit exceeded Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle who care about creating, delivering, and maintaining software responsibly. Join them; it only takes
429 Too Many Requests Squarespace
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 Suggested HTTP REST status code for 'request limit reached' up vote 32 down vote favorite 7 I'm putting together a spec for a REST service, part of which will incorporate the ability to throttle users service-wide and on groups api rate limit implementation of, or on individual, resources. Equally, time-outs for these would be configurable per resource/group/service. I'm just looking through the HTTP 1.1 spec and trying to decide how I will communicate to a client that a request will not be fulfilled because they've reached their limit. Initially I figured that client code 403 - Forbidden was the one, but this, from the spec: Authorization will not help and the request SHOULD NOT be repeated bothered me. It actually appears that 503 - Service Unavailable is a better one to use - since it allows for the communication of a retry time through the use of the Retry-After header. It's possible that in the future I might look to support 'purchasing' more requests via eCommerce (in which case it would be nice if client code 402 - Payment Required had been finalized!) - but I figure that this could equally be squeezed into a 503 response too. Which do you think I should use? Or is there another I've not considered? web-services rest http share|improve this question asked Jan 5 '12 at 11:36 Andras Zoltan 5281514 add a comment| 2 Answers 2 active oldest votes up vote 53 do
here for a quick overview of the site api rate limit best practices Help Center Detailed answers to any questions you might
Error Code 429 Activex Component Can't Create Object
have Meta Discuss the workings and policies of this site About Us Learn more
429 Error
about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users http://programmers.stackexchange.com/questions/128512/suggested-http-rest-status-code-for-request-limit-reached Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How to avoid HTTP error 429 (Too Many Requests) python up vote 23 http://stackoverflow.com/questions/22786068/how-to-avoid-http-error-429-too-many-requests-python down vote favorite 10 I am trying to use Python to login to a website and gather information from several webpages and I get the following error: Traceback (most recent call last): File "extract_test.py", line 43, in
2012 Additional HTTP Status Codes Abstract This document specifies additional HyperText Transfer Protocol (HTTP) status codes for a variety https://tools.ietf.org/html/rfc6585 of common situations. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the rate limit Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6585. Copyright Notice Copyright (c) 2012 IETF Trust and the error code 429 persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Nottingham & Fielding Standards Track [Page 1] RFC 6585 Additional HTTP Status Codes April 2012 Table of Contents 1. Introduction ....................................................2 2. Requirements ....................................................2 3. 428 Precondition Required .......................................2 4. 429 Too Many Requests ...........................................3 5. 431 Request Header Fields Too Large .............................4 6. 511 Network Authentication Required .............................4 7. Security Considerations ....................