-
-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
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
Wrong Documentation SecUploadKeepFiles #1205
Comments
Hey @security-database! Thanks for creating this issue! Are you up for a PR? |
@security-database ping. |
@fzipi i think i can do a PR ;) But i don't know what is good / wrong. Is the Doc good but Code wrong ? Or reverse ? Because if you stick to modsecurity, code is wrong - and for that, i cannot do a PR To be clear, i cannot write and submit code change, but can test changes. |
That is definitely a bad copy and paste. The modsecurity code should be the good behavior and docs. |
So |
But as you can see,
So it's not implemented every time. If so, you could just for the moment update the doc and plan to add it on later version ? |
Yes, updating the doc to match reality would be the first thing to do. Because this might have different outputs depending on the middleware, I don't think that at the Coraza layer we can make a decision. That's probably why in libModSecurity is not implemented. |
Agree |
Description
Trying to play with coraza-spoa it seem that the SecUploadKeepFiles RevelentOnly doc is wrong
Expected result
SecUploadKeepFiles RevelentOnly (By the doc)
Actual result
RevelentOnly On/Off (by the code)
Thanks for your work
The text was updated successfully, but these errors were encountered: