6 commits

Author	SHA1	Message	Date
Joseph Schorr	2f297ab4fe	Increase the rate limit on the API	2018-07-18 15:44:20 -04:00
Joseph Schorr	33a8099f35	Temporarily double the request limit. We'll start ratcheting it down over time.	2018-06-20 14:31:51 -04:00
Joseph Schorr	1d94e4d605	Audit out endpoints and ensure everything has a defined rate limit (even if quite large) ... For registry operations, these were the numbers found at time the PR was written: download_blob 108 per second across fleet v2_auth 180 per second across fleet catalog 1 per second across fleet fetch_manifest 205 per second across fleet list_all_tags 150 per second across fleet With an average fleet size of 25. As a result, we went with a registry limit of 10r/s (10 * 25 = 250 requests) to bound even the most prolific puller. Fixes https://jira.coreos.com/browse/QUAY-976	2018-06-20 13:36:24 -04:00
Joseph Schorr	ef167ab7e3	Rate limit the catalog endpoint by auth token and IP address	2018-06-05 18:24:31 -04:00
Jimmy Zelinskie	e36bf25a5e	nginx: rate limit 1r/s ... This reduces our rate limiting down to to 1 request per second.	2017-12-13 13:15:32 -05:00
Jimmy Zelinskie	6a681bb748	move nginx	2016-08-10 16:14:54 -04:00

Renamed from conf/rate-limiting.conf (Browse further)