Describe the bug
Enable WAF in front of developer portal at paranoia level = 2 and you'll get failures in WAF without additional rule configuration.
To Reproduce
Steps to reproduce the behavior:
See above
Expected behavior
Portal should provide a valid ruleset config that is compatible with our WAF filter. This can just be a config that's published in our docs.
Additional context
We should test at paranoia level 2 and 3
kcbabo
commented
2 years ago
Describe the bug Enable WAF in front of developer portal at paranoia level = 2 and you'll get failures in WAF without additional rule configuration.
To Reproduce Steps to reproduce the behavior: See above
Expected behavior Portal should provide a valid ruleset config that is compatible with our WAF filter. This can just be a config that's published in our docs.
Additional context We should test at paranoia level 2 and 3