Support rate limiting on combined / default vhost
Bug #2020283 reported by
Haw Loeung
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Content Cache Charm |
In Progress
|
High
|
Haw Loeung |
Bug Description
Hi,
We should add the ability to apply rate limiting to the default vhost / combined / default redirect stanzas in HAProxy.
This helps reduce issues with disk filling up due to logging when under DoS attack.
Related branches
~hloeung/content-cache-charm:rate-limiting
On hold
for merging
into
content-cache-charm:master
- Canonical IS Reviewers: Pending requested
- Content Cache Charmers: Pending requested
-
Diff: 314 lines (+117/-21)8 files modifiedlib/haproxy.py (+28/-17)
reactive/content_cache.py (+10/-1)
tests/unit/files/config_test_basic_config.txt (+6/-0)
tests/unit/files/content_cache_rendered_haproxy_test_output_rate_limiting.txt (+13/-1)
tests/unit/files/content_cache_rendered_haproxy_test_output_rate_limiting_missing_condition.txt (+10/-1)
tests/unit/test_content_cache.py (+24/-0)
tests/unit/test_haproxy.py (+23/-1)
tests/unit/test_nginx.py (+3/-0)
Changed in content-cache-charm: | |
assignee: | nobody → Haw Loeung (hloeung) |
status: | New → Triaged |
importance: | Undecided → High |
status: | Triaged → In Progress |
To post a comment you must log in.