Stability for usage in production

[gedw99]

I am wondering if this is ready for real world usage. I know that a very hard question to answer of course, but maybe you have an option and more knowledge on this than me.

It’s not listed here: https://coraza.io/connectors/ so it’s also why I am asking if this is ready for devs to use it.

i use and appreciate Caddy and think an Application firewall for Caddy is a massive boost to the adoption and future of Caddy.

Thank you in advance ..

[jptosso]

Hey Gerard! I'm confident with this caddy module. I use it myself.
We don't have an active maintainer but we keep monitoring bugs and development.

[fuomag9]

Unfortunately for me the current issues are a deal breaker as the rules I was using on nginx do not work on coraza-caddy :( (see #35)

[jcchavezs]

@fuomag9 @gedw99 thanks for raising this concerns. I would say at this point this library is still experimental and it is more in the stage of "if we want this to be production ready we should collaborate to make that happen". You trying this library and reporting bugs is indeed a great help but at the moment we are fighting in different fronts (CRS4, proxy-wasm, overall performance, etc.). If you are up to help I am more than happy to guide you towards that (this is what is working for us in coraza-spoa for example).

Some of the things that should be tackled on this repo is:

1. E2E smoke tests to ensure the integration works on every merge
2. Be up-to-date with latest coraza
3. Example setup to run the integration with one command (e.g. make run-example)
4. (Optional) Support to run FTW test suite.

[gedw99]

Thanks for the answer everyone. I will try it out

[jcchavezs]

We completely rewrite the connector and this is in line with the new coraza version, also much easier to keep up to date with coraza which some companies already use in prod.

[jcchavezs]

We are approaching to Version 2.0.0. We just release RC1 so please do try it and give feedback.