-
-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ToDo: Restore Rarbg HTTP 200 Rate Limiting [Waiting on Rarbg] #1277
Comments
Fixes: Prowlarr#1277 Finishes: Prowlarr#1169 Related: Prowlarr#1380 reverts 5cc044a
Fixes: Prowlarr#1277 Finishes: Prowlarr#1169 Related: Prowlarr#1380 reverts 5cc044a
Fixes: Prowlarr#1277 Finishes: Prowlarr#1169 Related: Prowlarr#1380 partially reverts 5cc044a
Fixes: Prowlarr#1277 Finishes: Prowlarr#1169 Related: Prowlarr#1380 partially reverts 5cc044a
Fixes: Prowlarr#1277 Finishes: Prowlarr#1169 Related: Prowlarr#1380 partially reverts 5cc044a
Fixes: Prowlarr#1277 Finishes: Prowlarr#1169 Related: Prowlarr#1380 partially reverts 5cc044a
Fixes: Prowlarr#1277 Finishes: Prowlarr#1169 Related: Prowlarr#1380 partially reverts 5cc044a
for posterity and context in the future
Originally posted by rarbg in Jackett/Jackett#13663 (comment) |
Is there an existing issue for this?
Is your feature request related to a problem? Please describe
Restore HTTP 200 & rate_limit 1 as too many requests.
reverted 5cc044a#diff-bd56c63a2154391186c3916be78aa2c0b6de3dca774930b0a4cb99b29d1b8425L46
Due to false positive rate_limit of 1 with 200s when no rate limit was actually occurring (results were found)
awaiting internal fix from rarbg for false positive
Describe the solution you'd like
if the API returns 200 with a json that contains rate_limit 1 retry in 5 minutes
#1169
Describe alternatives you've considered
N/A
Anything else?
N/A
AB#4613
The text was updated successfully, but these errors were encountered: