Default Configuration

From v3.x, mod_perimeterx is shipped out in Monitor Mode turned on and BlockingScore set to 100.
For users who wish to set the module to active blocking mode, additional changes will be required to the module configurations.

Basic example v3.x - Blocking Mode

        <IfModule mod_perimeterx.c>
            PXEnabled On
            AppID [APPID PLACEHOLDER]
            AuthToken [AUTHTOKEN PLACEHOLDER]
            CookieKey [COOKIE KEY PLACEHOLDER]
            MonitorMode Off
        </IfModule>

Basic example v3.x - Monitor Mode

        <IfModule mod_perimeterx.c>
            PXEnabled On
            AppID [APPID PLACEHOLDER]
            AuthToken [AUTHTOKEN PLACEHOLDER]
            CookieKey [COOKIE KEY PLACEHOLDER]
        </IfModule>

Custom Block Page Upgrade

Upgrading to version 3.x will require additional changes if CustomBlockPage is enabled.
From v3.x, the enforcer will not handle captcha validations, instead all captcha solving requests will be send directly to the PerimeterX service from the Javascript handler.


Did this page help you?