Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to set rate limit on scope #1006

Open
r3t4k3r opened this issue May 2, 2024 · 2 comments
Open

Add ability to set rate limit on scope #1006

r3t4k3r opened this issue May 2, 2024 · 2 comments

Comments

@r3t4k3r
Copy link

r3t4k3r commented May 2, 2024

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help us know what to work on
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request

Description

Feature like this, already exists in Zap proxy. I suggest add ability to set rate limit on domains in scope. Now idk how to do it better, add rate limit to scope or by domain names?

Use cases

Some sites WAF have rate limit. And if user ignoring it, then website block user.

@Sytten
Copy link
Member

Sytten commented May 2, 2024

Thats an interesting idea, is it only for the proxy part or also for tools like automate?

@r3t4k3r
Copy link
Author

r3t4k3r commented May 2, 2024

Thats an interesting idea, is it only for the proxy part or also for tools like automate?

I think u can do checkbox list to set/unset rate limit on any parts of tools.

For example:

  • automate
  • requests from proxy
  • plugin_name
  • another plugin name

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants