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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Suggestion] challenge based on total requests from all IPs #960

Open
1718666698 opened this issue Jul 3, 2024 · 5 comments
Open

[Suggestion] challenge based on total requests from all IPs #960

1718666698 opened this issue Jul 3, 2024 · 5 comments
Labels
enhancement New feature or request

Comments

@1718666698
Copy link

1718666698 commented Jul 3, 2024

背景与遇到的问题

在网站访客少的时候不开启人机验证让用户有更好的访问体验

建议的解决方案

可以加个根据限定时间内访问量自动开启人机验证功能,在访问量少时自动关闭

@Lorna0
Copy link
Collaborator

Lorna0 commented Jul 4, 2024

直接 配置限频-人机验证 呢

@1718666698
Copy link
Author

那个限频只针对某一ip的访问的,我想要针对全站访问量来统计的

@Lorna0
Copy link
Collaborator

Lorna0 commented Jul 5, 2024

没想到有啥具体的 case 会需要这个功能诶。人机验证主要是防 bot 用的,确实是针对特定有问题的 IP 比全站开启好点。是出于高峰期性能压力的考虑吗,但是人机验证并不太能缓解服务器性能压力。

@DR-lin-eng
Copy link

没想到有啥具体的 case 会需要这个功能诶。人机验证主要是防 bot 用的,确实是针对特定有问题的 IP 比全站开启好点。是出于高峰期性能压力的考虑吗,但是人机验证并不太能缓解服务器性能压力。

他这个是考虑到平时正常访问量下不会触发人机验证,当被ddos时访问量会激增能自动化拉起人机盾,毕竟谁也不知道什么时候会被ddos攻击,ddos攻击有时候是ip量巨大的大部分ip可能是触发不了cc速率限制的

@Lorna0
Copy link
Collaborator

Lorna0 commented Jul 30, 2024

Gathering interst. Btw this issue seem to be work for this case:

@Lorna0 Lorna0 added enhancement New feature or request and removed need more information labels Jul 30, 2024
@Lorna0 Lorna0 changed the title [建议] 增加根据访问量自动开启关闭人机验证功能 [Suggestion] challenge base on total requests count from all IP Jul 30, 2024
@Lorna0 Lorna0 changed the title [Suggestion] challenge base on total requests count from all IP [Suggestion] challenge based on total requests from all IPs Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants