Rate limit Gitea repo archives #32
Labels
No Label
Breaking
Domain
komu.boo
Domain
langrock.info
Domain
libre.moe
Involves
Documentation
Involves
Security
Involves
Testing
Kind
Bug
Kind
Enhancement
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Service
Drone
Service
Element
Service
Gitea
Service
Matrix
Service
Nextcloud
Service
Szuru
Status
Abandoned
Status
Acknowledged
Status
Blocked
Status
Duplicate
Status
Invalid
Status
Need More Info
Status
Won't Fix
No Milestone
No project
No Assignees
1 Participants
Notifications
Total Time Spent: 10 minutes
Due Date
lukas
10 minutes
No due date set.
Dependencies
No dependencies set.
Reference: KomuSolutions/igot99issues#32
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Repo archives have the ability to consume a lot of server resources. If multiple large archives, that have to be built on demand, are requested at the same time, the server will run out of memory.
A kind of rate limit for this has to be implemented, either by watching the container resource usage or simply by limit download requests to about 1 request per 5minutes per IP.
This has now been implemented.
Up to 3 downloads per minute are allowed per IP.
There is currently a bug, making every request to Gitea (or maybe even in general) count towards the limit, meaning fast navigation through Gitea will make any downloads fail, not just more than 3.
Due to the new infrastructure, rate limits have been removed again.