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

Frang: per resource/location/vhost rate limiting #688

Closed
krizhanovsky opened this issue Feb 25, 2017 · 1 comment
Closed

Frang: per resource/location/vhost rate limiting #688

krizhanovsky opened this issue Feb 25, 2017 · 1 comment

Comments

@krizhanovsky
Copy link
Contributor

Currently Frang supports only global rate limiting configuration. However, different locations, vhosts and server groups may require different settings. First of all, if one of the serviced host faces the attack and we need to load specific Frang rules, the rules must affect the victim host only. Secondly, heavy dynamic and static content are usually requested with different frequencies, so it has sense to set different limits by HTTP match rules.

@krizhanovsky krizhanovsky added this to the 0.6 WebOS milestone Feb 25, 2017
@krizhanovsky krizhanovsky changed the title [Frang]: per resource/location/vhost rate limiting Frang: per resource/location/vhost rate limiting Feb 25, 2017
@krizhanovsky krizhanovsky modified the milestones: backlog, 0.6 KTLS Jan 9, 2018
@krizhanovsky
Copy link
Contributor Author

Since the issue depends on vhost's, part of #471, in part of vhost syntax, must be implemented.

This was referenced Mar 29, 2018
aleksostapenko added a commit that referenced this issue Apr 25, 2018
aleksostapenko added a commit that referenced this issue May 7, 2018
 Fix #688: Make frang directives location-specific.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants