Fix redirect loop in Gitea rate limit
What does this MR do and why?
The current implementation applies a rate limit to the status endpoint to limit repository list fetches from Gitea per minute.
This change increases the rate limit threshold to prevent regular users from being rate limited during normal usage.
This resolves the infinite redirect issue and improves the overall user experience.
References
Screenshots or screen recordings
How to set up and validate locally
Initial setup
- Set up a local Gitea instance with a cloneable project.
Testing imports
- Perform some Gitea imports.
- Verify that the real-time status updates work.
- Verify that the project is successfully imported.
Testing invalid access token
- Visit http://gdk.test:3000/import/gitea/status.
- Enter your URL and Gitea access token.
- Delete the access token in Gitea and refresh the page
- You should be redirected to the initial page
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Rodrigo Tomonari