Juan Pablo Tosso

We are passing CRS tests, so it doesn't seem like a v3 problem.

Already implemented https://github.com/VermaShivansh/coraza-ratelimit-plugin

Most important ingress controllers have waf integrations - https://kubernetes.github.io/ingress-nginx/user-guide/third-party-addons/modsecurity/ - https://www.getambassador.io/docs/edge-stack/latest/howtos/web-application-firewalls/ - Envoy: https://github.com/corazawaf/coraza-proxy-wasm https://www.cncf.io/blog/2022/09/22/how-to-think-about-securing-kubernetes-with-waf-and-dos-protection/

We are talking about hundreds of rules and many required options. Also, we would like to keep consistency across connectors. CRS requires tens of directives to setup coraza, default actions...

Outstanding contributions, everyone. Thank you @dune73. I have experience as an enterprise integrator, and one of the biggest struggles is false positive management, even for P1. I have never seen...

For NPCs I would just use the player class and create a bot, instead of receiving inputs by a browser, receive inputs by the server :) 2016-07-03 11:30 GMT-04:00 jgamedev...

I agree with you, I would add a second server and IPC communication as it would rather slow down the server main thread. It could be written in the same...

Just edit AbstractGame.js `function getStateForPlayer (player) { return { serverTime: getTime(), ownPlayer: player.toJSON(), players: Array.from(players.values()).filter(otherPlayer => { return otherPlayer !== player; }).map(player => player.toJSON()), events: eventsFired.filter((event) => { return event.getFiredBy()...

Can we validate if this is still happening in https://github.com/corazawaf/coraza-caddy/releases/tag/v1.2.2 ?

In the following example I demonstrate that reload is working: ``` ubuntu@ip-172-xxx-xxx-xxx:~/tosso.io$ docker exec -w /etc/caddy $caddy_container_id caddy reload {"level":"info","ts":1689338814.9287016,"msg":"using adjacent Caddyfile"} ``` I added the following rule: `SecRule REQUEST_URI...