IQSS / IQSS/dataverse-frontend
Feature Request/Idea: implement `:RateLimitingDefaultCapacityTiers` in the new front-end
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Overview of the Feature Request
We're seeing increased traffic from what are believed to be LLM scrapers. Current rate limiting logic applies to API endpoints only, but could similar logic help the new front-end protect from such attacks?
What kind of user is the feature intended for?
Sysadmin
What inspired the request?
A deluge of GET requests from a broad swath of client IPv4s, each client making some small (<20) number of requests before switching addresses.
What existing behavior do you want changed?
Database servers lit up like Christmas trees.
Any brand-new behavior do you want to add to Dataverse?
Configurable rate limiting in the new front-end, if its current architecture might make this possible in any way.
Any open or closed issues related to this feature request?
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 reviewing pull request #10211 and the new front-end architecture, since no implementation files or tests are identified here. Determine whether configurable rate limiting can protect non-API GET requests, define the intended behavior for the reported scraping pattern, and document how completion would be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100