[GH-ISSUE #103] 集群环境CC配置不共享问题 #78

Closed
opened 2026-03-04 12:18:45 +03:00 by kerem · 4 comments
Owner

Originally created by @ccyuvin on GitHub (Aug 4, 2022).
Original GitHub issue: https://github.com/ADD-SP/ngx_waf/issues/103

环境背景:有多个nginx节点共同提供服务,用户通过四层LB轮询到多个nginx节点。
问题:配置了waf_action cc_deny=CAPTCHA,当用户触发CC请求次数的上限,进行验证码效验时,效验的POST /captcha 请求有可能轮询到另一个nginx节点,另一个节点未达到CC请求次数的上限,则会返回405响应,用户会一直卡在验证页面。刷新页面后又会重新要求进行验证码效验。
此外,CC请求次数的上限和验证码功能目前是记录在waf_zone,也就是本机内存中,无法进行多节点共享。后续是否可以考虑放入redis或者其他方式进行集群共享?

Originally created by @ccyuvin on GitHub (Aug 4, 2022). Original GitHub issue: https://github.com/ADD-SP/ngx_waf/issues/103 环境背景:有多个nginx节点共同提供服务,用户通过四层LB轮询到多个nginx节点。 问题:配置了waf_action cc_deny=CAPTCHA,当用户触发CC请求次数的上限,进行验证码效验时,效验的POST /captcha 请求有可能轮询到另一个nginx节点,另一个节点未达到CC请求次数的上限,则会返回405响应,用户会一直卡在验证页面。刷新页面后又会重新要求进行验证码效验。 此外,CC请求次数的上限和验证码功能目前是记录在waf_zone,也就是本机内存中,无法进行多节点共享。后续是否可以考虑放入redis或者其他方式进行集群共享?
kerem 2026-03-04 12:18:45 +03:00
  • closed this issue
  • added the
    stale
    label
Author
Owner

@stale[bot] commented on GitHub (Aug 11, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
此 issue 因为最近没有任何活动已经被标记,如果在此之后的一段时间内仍没有任何活动则会被关闭。感谢您对项目的支持。

<!-- gh-comment-id:1211498375 --> @stale[bot] commented on GitHub (Aug 11, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. 此 issue 因为最近没有任何活动已经被标记,如果在此之后的一段时间内仍没有任何活动则会被关闭。感谢您对项目的支持。
Author
Owner

@stale[bot] commented on GitHub (Aug 30, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
此 issue 因为最近没有任何活动已经被标记,如果在此之后的一段时间内仍没有任何活动则会被关闭。感谢您对项目的支持。

<!-- gh-comment-id:1232201989 --> @stale[bot] commented on GitHub (Aug 30, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. 此 issue 因为最近没有任何活动已经被标记,如果在此之后的一段时间内仍没有任何活动则会被关闭。感谢您对项目的支持。
Author
Owner

@stale[bot] commented on GitHub (Sep 13, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
此 issue 因为最近没有任何活动已经被标记,如果在此之后的一段时间内仍没有任何活动则会被关闭。感谢您对项目的支持。

<!-- gh-comment-id:1245021089 --> @stale[bot] commented on GitHub (Sep 13, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. 此 issue 因为最近没有任何活动已经被标记,如果在此之后的一段时间内仍没有任何活动则会被关闭。感谢您对项目的支持。
Author
Owner

@stale[bot] commented on GitHub (Sep 26, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
此 issue 因为最近没有任何活动已经被标记,如果在此之后的一段时间内仍没有任何活动则会被关闭。感谢您对项目的支持。

<!-- gh-comment-id:1258288253 --> @stale[bot] commented on GitHub (Sep 26, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. 此 issue 因为最近没有任何活动已经被标记,如果在此之后的一段时间内仍没有任何活动则会被关闭。感谢您对项目的支持。
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ngx_waf#78
No description provided.