Articles about laravel

A few years ago I wrote about a simple idea: instead of maintaining huge fail2ban regexes for every weird scanner path, let your Laravel app return a very specific HTTP status code when a request clearly looks like automated probing, then let fail2ban ban the IP based on that status code.

Everybody knows them, nobody likes them: cookie banners. They are only required if technically unnecessary cookies are to be used. However, opinions differ when cookies are necessary. Obviously, the safest way to go is without cookies at all. How to disable cookies in Laravel and what to look out for, is explained in this article.

Every website is bombarded with dozens of unwanted requests every day. The talk here is of so-called [vulnerability scanners](https://owasp.org/www-project-automated-threats-to-web-applications/assets/oats/EN/OAT-014_Vulnerability_Scanning). In this article you will learn what they are all about and how you can fight the uninvited guests.