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
Respect indexer API limits for Newznab #910
Comments
Users can set Query and Grab limits in-app on a Per Indexer basis - which is a just fine solution this would only be applicable to Newznab Indexers |
It would, which covers 99% of indexers. Users can't be trusted to set limits, or correct limits. Hence this request to respect the limits the indexer shows for that user. |
We support 500+ indexers, Newznab being less than 10% of them. That was bakers point Leaving this open as we could likely set the default values for Query and Grab Limit from a call during indexer add for the Newznab engine |
You mean Trackers? Good Usenet indexer can be counted on two hands.
That would be a good start :-) |
Pretty sure we respect when they indicate rate limit has been reached. Is there anything else to do here? Grabbing the limits would be a maybe as they do not exist in newznab spec |
Is there an existing issue for this?
Is your feature request related to a problem? Please describe
Prowlarr keeps hitting API endpoints even when the user has run out of requests for the day
Describe the solution you'd like
Sonarr/Sonarr#3132 (comment)
Describe alternatives you've considered
None. Prowlarr can use the indexer API limits shown in every API response at the top of the XML response.
Anything else?
None.
AB#2857
The text was updated successfully, but these errors were encountered: