- This topic is empty.
June 2026 promo! Join our Discord free of charge.
Thinking on this.
After some recent DDOS against slickstack.io search results, wondering if rewriting the URL could make rate-limiting rules in Nginx more effective
why would it need rewriting?
why would it need rewriting?
because you need a location block for assign the rate limiter zone in Nginx.
unless you have a complex map type of approach:
https://stackoverflow.com/questions/46178259/nginx-limit-requests-by-parameter-in-body-or-query
https://github.com/littlebizzy/slickstack/blob/master/modules/nginx/sites/production.txt#L211
That map solution is intriguing, never seen that before…
map $arg_ctl $do_limit {
"param1" $binary_remote_addr;
default "";
}
limit_req_zone $do_limit zone=mylimit:10m rate=10r/s;
server {
listen 8044;
limit_req_log_level warn;
location /route/{
limit_req zone=mylimit burst=1000;
proxy_pass https://the_Cool_server/;
}}
not if they be DOS’in you boys
If you want the LittleBizzy team to setup your SlickStack cloud server for you and migrate all your data, we can do it for a fixed price at the below link. If you're not satisfied, request a 100% refund anytime you want (no questions asked).
We champion core values like free speech, transparency, and portability, and welcome anyone else who does too.
Here is a non-exhaustive list of plugins, themes, and other services that we recommend checking out.
Every stack script and server deployment platform is a bit different, so check to see how SlickStack compares.
Here’s some of the incredible performance features you can expect after launching your SlickStack cloud VPS.
If you are wondering what specific problems SlickStack can help solve, browse some of the solutions below.
In lieu of donations, please show your support by mentioning SlickStack on your blog or write a review. Thank you!