Tim Burke 778767f324 s3api: Better handle 498/429 responses ... Currently, they just 500 as an unexpected response status. Much better would be S3's '503 Slow Down' response. Of course, that's all dependent on where you place ratelimit in your pipeline -- and we haven't really given clear guidance on that. I'm not actually sure you *want* ratelimit to be after s3api and auth... but if you *do*, let's at least handle it gracefully. Change-Id: I36f0954fd9949d7d1404a0c381b917d1cfb17ec5 Related-Bug: 1669888 (cherry picked from commit f33c061ae9)		2020-01-28 10:39:25 -08:00
..
account	Clean up account-reaper a bit	2019-02-21 13:36:14 -08:00
cli	manage-shard-ranges: nicer message if we can't get_info()	2019-02-28 23:29:53 +00:00
common	s3api: Better handle 498/429 responses	2020-01-28 10:39:25 -08:00
container	Merge "Sharding: Clean up old CleaveConext's during audit" into stable/stein	2019-10-23 17:43:55 +00:00
locale	Imported Translations from Zanata	2019-08-04 07:54:31 +00:00
obj	Merge "Remove invalid dict entries from hashes.pkl" into stable/stein	2019-08-17 04:31:48 +00:00
proxy	Merge "Clean up how we walk through ranges in ECAppIter"	2019-03-20 23:56:38 +00:00
__init__.py	py3: Monkey-patch json.loads to accept bytes on py35	2018-11-02 21:38:53 +00:00