Respond with HTTP 429 for Grab/Query Limits when api is called (Current State: HTTP 200) #783

Closed
opened 2026-02-20 10:03:31 -05:00 by deekerman · 0 comments
Owner

Originally created by @bakerboy448 on GitHub (Feb 9, 2023).

          hi folks! so I've been working on https://github.com/cross-seed/cross-seed/issues/327 and it looks like the implementation in this PR responds with HTTP 200 (rather than 429) on both query and grab, with the following body. [Radarr's existing logic](https://github.com/Radarr/Radarr/blob/627ab64fd023269c8bedece61e529329600a3419/src/NzbDrone.Core/Download/UsenetClientBase.cs#L61), along with the logic I've been writing, expects the status code of the HTTP request to come back as 429.
> GET /prowlarr/3/download?[REDACTED] HTTP/2
> ... request headers ...

< HTTP/2 200
< ... response headers ...

<?xml version="1.0" encoding="UTF-8"?>
<error code="429" description="Grab limit reached (5)" />

Originally posted by @mmgoodnow in https://github.com/Prowlarr/Prowlarr/issues/1168#issuecomment-1417036950

AB#4891

Originally created by @bakerboy448 on GitHub (Feb 9, 2023). hi folks! so I've been working on https://github.com/cross-seed/cross-seed/issues/327 and it looks like the implementation in this PR responds with HTTP 200 (rather than 429) on both query and grab, with the following body. [Radarr's existing logic](https://github.com/Radarr/Radarr/blob/627ab64fd023269c8bedece61e529329600a3419/src/NzbDrone.Core/Download/UsenetClientBase.cs#L61), along with the logic I've been writing, expects the status code of the HTTP request to come back as 429. ``` > GET /prowlarr/3/download?[REDACTED] HTTP/2 > ... request headers ... < HTTP/2 200 < ... response headers ... <?xml version="1.0" encoding="UTF-8"?> <error code="429" description="Grab limit reached (5)" /> ``` _Originally posted by @mmgoodnow in https://github.com/Prowlarr/Prowlarr/issues/1168#issuecomment-1417036950_ [AB#4891](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/4891)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Prowlarr#783
No description provided.