-
Posts
-
-
.thumb.png.b8c670f34de56a5b725691b17807071d.png)
So you developed a rate limiter with extra steps on the application layer ? Do you know that http is on top of tcp and someone can exhaust your resources before even reach your app ? Thus whatever limit/rule you set is a bit obsolete and creates complexity for your app. Also the order is cloudflare/ os firewall / nginx / php -
-
-
Some pictures and I uplade also some interface to be tested. Interfaces to download (ofc compiled just to test): Protocol 166: https://drive.google.com/file/d/1_ZMfCJVplQg8uXnP3nn2w9OByIyKhqXV/view?usp=sharing Protocol 447 Classic: https://drive.google.com/file/d/1tG07r4GgdgCv_9IHdUROFfxe_yKqkno1/view?usp=sharing Protocol 542 Live: https://drive.google.com/file/d/1d9woGO5icCP6l9VT2tDpcqPaFtXYVGiG/view?usp=sharing Protocol 557 Live: https://drive.google.com/file/d/1s4HkuIUXtCWUO_qwZ9bX3JNjQ9VXlk6f/view?usp=sharing Protocol 557 Classic: https://drive.google.com/file/d/1xwaJh09wabvKlz80K_nbQq2JtNRnwhF-/view?usp=sharing Images:
-
-
Topics
-
.thumb.jpg.020771498d0f162940c909002777c55e.jpg)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now