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
We would like to request support for the TIME variable and other time-related variables (TIME_DAY, TIME_EPOCH, etc.) in Coraza WAF. These variables are critical for logging and rule creation, improving the granularity and usability of logs.
Basic example
For example, the rule like that would benefit from such variables:
These variables would provide more comprehensive information in logs:
[ModSecurity] [1699951234] Request blocked.
Motivation
Adding support for TIME and related variables would enhance Coraza's functionality, aligning it more closely with ModSecurity features. This is particularly useful for implementing time-based rules and improving the context of logged events, such as debugging and rule evaluation.
Could you also advise on the preferred approach for implementation? We are interested in contributing via a pull request and would like to align with project guidelines.
The text was updated successfully, but these errors were encountered:
Summary
We would like to request support for the
TIME
variable and other time-related variables (TIME_DAY
,TIME_EPOCH
, etc.) in Coraza WAF. These variables are critical for logging and rule creation, improving the granularity and usability of logs.Basic example
For example, the rule like that would benefit from such variables:
These variables would provide more comprehensive information in logs:
Motivation
Adding support for TIME and related variables would enhance Coraza's functionality, aligning it more closely with ModSecurity features. This is particularly useful for implementing time-based rules and improving the context of logged events, such as debugging and rule evaluation.
Could you also advise on the preferred approach for implementation? We are interested in contributing via a pull request and would like to align with project guidelines.
The text was updated successfully, but these errors were encountered: