Skip to content

Conversation

@victorhora
Copy link
Contributor

Rationale is being explicit on which configurations are currently supported and allowing a smoother transition between v2 to v3, mainly for older or highly modified setups that uses unusual configuration directives.
Also, some unsupported directives that uses CONFIG_VALUE (e.g. SecConnEngine) now allows the user to keep the configuration directive as long as its set to 'Off'.

*/
| CONFIG_DIR_UNICODE_MAP_FILE
/* Parser error disabled to avoid breaking default installations with modsecurity.conf-recommended
driver.error(@0, "SecUnicodeMapFile is not yet supported. utils::string::x2c");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utils::string::x2c ? kkk

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops! :P

@zimmerle
Copy link
Contributor

zimmerle commented Mar 8, 2018

merged. thanks.

@zimmerle zimmerle closed this Mar 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants