Rate limit for 'POST'
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 44
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Currently we already applied the rate limit for API in api and node. As we expected, the most request for api is GET and easily can be reached to the limit like getting account information. I think we should open to submit the transactions in spite of over rate limit of client.
There are various way to support this feature, I suggest simple way.
- add new option,
--rate-limit-api-post, it has the same format with--rate-limit-api -
network.RateLimitMiddlewarechecks the method,POST
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 with the existing --rate-limit-api option and network.RateLimitMiddleware. Trace how the current API rate limit is configured and applied, then add the POST-specific option and verify that POST transaction requests use it while other methods retain the existing limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100