Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
litespeed_wiki:config:mod_security_faq [2018/10/08 20:55] Lisa Clarke [Unsupported Variable error] Proofreading |
litespeed_wiki:config:mod_security_faq [2018/11/27 21:22] Lisa Clarke [You should not place 'SecDebugLogLevel' inside "LocationMatch" context] Proofreading |
||
---|---|---|---|
Line 45: | Line 45: | ||
The above error messages simply mean the given variables are not supported by LSWS yet. The errors can simply be ignored. We periodically review our mod_security engine and frequently add new support. Stay tuned. | The above error messages simply mean the given variables are not supported by LSWS yet. The errors can simply be ignored. We periodically review our mod_security engine and frequently add new support. Stay tuned. | ||
+ | |||
+ | ===== Does LSWS Support the "LocationMatch" directive? ===== | ||
+ | When you use ''SecDebugLogLevel'', ''SecAuditLogParts'' or ''SecAuditLog'' within the ''LocationMatch'' directive, you may see the following errors on LSWS: | ||
+ | |||
+ | Directive 'SecDebugLogLevel' is not allowed in current context. | ||
+ | Directive 'SecAuditLogParts' is not allowed in current context. | ||
+ | Directive 'SecAuditLog' is not allowed in current context. | ||
+ | |||
+ | LiteSpeed Web Server //does// support the ''LocationMatch'' context, however the above three directives may not be configured within it. On LSWS, audit log can only be set at the server level, and the debug log level can be set at vhost level. We have no plans to make these directives available at the matching context level, as it would be counterproductive to the optimization applied to the engine. |