Aggressive Akamai Rate Limiting
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 738
- Forks
- 407
- PR merge metrics
- No merged PRs in 30d
Description
hello. I was visiting the portal today and clicked around on like 5 or so pages and got hit with the Akamai rate limiting screen. All in all took about 60 seconds from the time I landed on the site until this error
I'm guessing this is probably due to the fact that client-side routing seems to be broken and navigating around via links triggers a full page reload everytime, which means all those assets are being requested again all the APIs get hit.
(also I know the rate limiting isn't a front-end issue but please consider not breaking the client-side routing experience since a full page reload processes ~7MB of JavaScript each time and I think defeats the purpose of using React 🙏 )
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
Reproduce the issue by opening the portal and navigating through about five pages, then inspect whether each link causes a full page reload and repeated asset or API requests. Done means client-side navigation works without triggering the reported repeated loading that quickly reaches Akamai rate limiting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100