You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the past during the transition from ModSecurity 1 to ModSecurity 2, it was chosen to rename the module as mod_security2.so. Naturally the version 3 will be called mod_security3 and so on.
After a recent discussion on the mailing list, some users bought to our attention that the name of the module should be only mod_security. That will make easy further upgrades, as it may not need to change anything configuration wise, only upgrade their systems with newer version.
The benefit of that should be well study, as the consequences. Depending on the results we should move forward to rename it or not.
The text was updated successfully, but these errors were encountered:
In the past during the transition from ModSecurity 1 to ModSecurity 2, it was chosen to rename the module as mod_security2.so. Naturally the version 3 will be called mod_security3 and so on.
After a recent discussion on the mailing list, some users bought to our attention that the name of the module should be only mod_security. That will make easy further upgrades, as it may not need to change anything configuration wise, only upgrade their systems with newer version.
The benefit of that should be well study, as the consequences. Depending on the results we should move forward to rename it or not.
The text was updated successfully, but these errors were encountered: