Most of your rules will use this configuration directive. This is a configuration directive which creates a rule that will analyze the selected variables using the selected operator. SecRule REQUEST_URI /index.php" "id:1,phase:1,t:lowercase,deny" For full listings of configuration directives, variables, operators, and transformations/actions, please refer to the reference section of this guide. Generally rules have 4 parts: a configuration directive, variable(s), operator(s), and action(s). The custom rule given checks whether or not history was changed by a request. This section explains an example custom rule. ModSecurity References"Ĭollapse section "4. Configuration Examples"Įxpand section "4. Configuration Examples"Ĭollapse section "3.1. ModSecurity Rules Making"Įxpand section "3.1. ModSecurity Rules Making"Ĭollapse section "3. Windows Configuration"Ĭollapse section "2.2.3. Windows Configuration"Įxpand section "2.2.3. Windows Configuration"Ĭollapse section "2.2. Initial Configuration"Įxpand section "2.2. Initial Configuration"Ĭollapse section "2.1.3. Installation with Red Hat JBoss Core ServicesĮxpand section "2.1.3. ModSecurity Configuration"Ĭollapse section "2.1. ModSecurity Configuration"Ĭollapse section "2. ModSecurity Introduction"Įxpand section "2. ModSecurity Introduction"Ĭollapse section "1. Providing feedback on Red Hat documentationĮxpand section "1. Red Hat JBoss Core Services ModSecurity Guide
0 kommentar(er)
