heads up, since this could impact Release Doc Maker. I haven't done a pass of the code yet. Will try to find time this week.
---------- Forwarded message --------- From: Daniel Gruno <[email protected]> Date: Sun, Jan 27, 2019 at 11:10 AM Subject: [Notice] Rate limiting in effect on JIRA, BZ, Moin To: [email protected] <[email protected]> Hi folks, Over the past few days we have implemented rate limiting on selected services across the ASF; starting with JIRA, BugZilla and Moin Wiki. IF YOU ARE A NORMAL USER: ######################### This very likely will never affect you, and you can go about your business just like normal :) If you DO experience errors or 429 (rate limited) response codes, please do let us know so we can address it. IF YOU ARE A ROBOT/CYBORG/COMPUTRON: #################################### There are now limits in place for how much CPU time you can use, varying from service to service. If you get limited, you will receive a HTTP 429 response instead of the normal 200, and a short text blob will explain that you have crossed our resource limits and have been rate-limited. It will also explain why, and when you can expect to be unblocked again (generally within two minutes time). Scrapers, bots etc using our services should check for a 429 response code and act accordingly (or just slow down the discovery pace in general, as that benefits all of us). Rate limits are applied across IP blocks to discourage distributed abuse, thus if you have 1.2.3.4 abusing a service, 1.2.3.5 would potentially also be affected by the rate limits till they expire. Later this year, we will be rolling out rate limits on more services, and we encourage people automating tasks to honor the 429 responses across all ASF services. With regards, Daniel on behalf of ASF Infra. -- busbey
