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
1.10.x (latest stable)
1.22.x
Both cors and modsecurity are added to the chain despite removeUnusedFilters: true and not having any explicit WAF or CORS configuration made.
cors
modsecurity
removeUnusedFilters: true
deploy gloo edge, configure settings, create simple VS, observe generated filter chain in evnoy config dump.
cors and modsecurity filters should not be injected into HTTP filter chain.
No response
The text was updated successfully, but these errors were encountered:
Related to this #5651
Sorry, something went wrong.
This is merged and released in Gloo EE 1.12 and 1.11
sam-heilbron
No branches or pull requests
Gloo Edge Version
1.10.x (latest stable)
Kubernetes Version
1.22.x
Describe the bug
Both
cors
andmodsecurity
are added to the chain despiteremoveUnusedFilters: true
and not having any explicit WAF or CORS configuration made.Steps to reproduce the bug
deploy gloo edge, configure settings, create simple VS, observe generated filter chain in evnoy config dump.
Expected Behavior
cors and modsecurity filters should not be injected into HTTP filter chain.
Additional Context
No response
The text was updated successfully, but these errors were encountered: