We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe we could replace waf.Rules pointer in runtime without affecting the users but I'm not sure if it might panic in some cases
Other mechanism would be to remove waf.Rules and replace it with:
func (w *Waf) Rules() *RuleGroup { w.rgMux.RLock() defer w.rgMux.RUnlock() return w.rules }
That way we could lock .Rules() whenever we are refreshing the rules with something like wwaf.SetRules(someRuleGroup).
.Rules()
wwaf.SetRules(someRuleGroup)
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open for 30 days with no activity.
Sorry, something went wrong.
This is still happening.
Maybe this problem should be solved by the connectors and not by Coraza ?
jptosso
fzipi
syinwu
No branches or pull requests
Maybe we could replace waf.Rules pointer in runtime without affecting the users but I'm not sure if it might panic in some cases
Other mechanism would be to remove waf.Rules and replace it with:
That way we could lock
.Rules()
whenever we are refreshing the rules with something likewwaf.SetRules(someRuleGroup)
.The text was updated successfully, but these errors were encountered: