-
Notifications
You must be signed in to change notification settings - Fork 20
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
feat: add well known deployment problems #111
base: main
Are you sure you want to change the base?
Conversation
Can we combine this with the 'Known issues' page? It feels a little redundant to have two pages on the same topic, known issues and known problems. Or maybe we retire one or update one? |
Yes, we can, and we should. Let me push the change. |
Signed-off-by: Felipe Zipitria <[email protected]>
Signed-off-by: Felipe Zipitria <[email protected]>
6e97354
to
098f7ba
Compare
@RedXanadu Moved to known issues. Also, moved from bullet points to titles, so they can be referenced easily from other places. |
@RedXanadu Can you review this one now? |
|
||
### Anomaly Mode Doesn't Work | ||
|
||
Sometimes on IIS or Nginx users run into an instance where anomaly mode doesn't work as expected. In fact upon careful inspection of logs one would notice that rules don't fire in the order we would expect. In general this is a result of using the `'*'` operator within these environments as it does not act the same way as in Apache. In general within both Apache and IIS one should expliticly include the various files present within the OWASP CRS instead of using the `'*'`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general within both Apache and IIS
should probably be Nginx and IIS
.
Also: Does this problem persist with newer versions? Because if it does, our INSTALL that proposes *
now is likely wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sadly, I do not have a clue. This was copied from the Website 🤷 . Maybe we need to clean this out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@airween what is the real status of Include rules/*.conf
on Nginx?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, what do you mean about "real status"?
The mentioned configuration (Include rules/*.conf
) on Nginx works as well, I use that form all of my servers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought so. That means this passage here can be omitted and we should update the website too.
The diff is significant... I thought this was just adding some new bullet points to the list, that would be an easy win and quick to review 😅 I'll review when I can. |
No description provided.