more elaborate rate-limiting response?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
I've implemented CheckRateLimitForCollectionPageCommand on two servers for tier 0 users. It works well and recovers automatically.
Currently a triggered instance returns a terse 429 response, but if Dataverse could print an explanation that content may still be viewable by signed-in users with a link to the login page, that might make such rate limiting less of a "nuclear" option?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating CheckRateLimitForCollectionPageCommand and the current 429 response it triggers for tier 0 users. Determine how the response is generated and how a login URL can be presented. Done means the rate-limiting response explains that content may be viewable by signed-in users and includes a link to the login page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100