Akamai EdgeWorker v4 configuration options

Your HUMAN Application ID in the form of PX12AB34CD. You can copy this value from the HUMAN Console in Platform Settings > Applications Overview. If you have multiple applications, make sure to copy the ID of the application you want the Enforcer on.

Security Settings: Hidden

The application’s server token needed to authorize with HUMAN’s backend. You can copy this value from the HUMAN Console in Platform Settings > Applications Overview > Click the appropriate application > Server token tab.

Security Settings: Hidden

The secret used to encrypt and decrypt the risk cookie sent from the HUMAN Sensor. You can copy this value from the HUMAN Console in Sightline Cyberfraud Defense > Traffic Policy Overview > Click the appropriate application > Click the key > Copy value.

If you need to rotate secrets, then adjust this configuration to be an array of strings (string[]) and include the new secret and old secret. The new secret value should be the first value in the array. This prevents decryption failures. For example, newCooki3Secr3t,0ldCooki3Secr3t.

Base URL for HUMAN SAPI (Risk API and related calls). If empty, the Enforcer uses the default host for your Application ID. Set this only when directed by HUMAN (for example, custom routing or non-standard environments). Update <PX_APP_ID> with your Application ID. For example, sapi-PX12345678.perimeterx.net.

The total time in milliseconds that the Enforcer will wait for the Risk API request to return before timing out and passing the request.

The severity at which the logger will output logs.

• none: The logger will not generate any logs.
• error: The logger will only generate logs on fatal errors.
• debug: The logger will generate detailed logs for debugging purposes. Not recommended for production environments.

See PX_LOGGER_AUTH_TOKEN for a header-based alternative.

An array of header names that are trusted to contain the true client IP. Headers are traversed in the order they’re listed, and the first header value will always be used as the client IP.

Taken from AK_CLIENT_REAL_IP variable by default.

For example, true-ip,true-client-ip.

Whether the Enforcer module is enabled.

• true: Enable the module
• false: Disable the module

The Enforcer’s operation mode.

• monitor: The Enforcer performs all functions without returning block responses. Useful for analyzing and adjusting Enforcer behavior without serving block pages to end users. If you have routes that must have enforcement at all times, see Enforced routes.
• active_blocking: The Enforcer will return block responses as needed.

In specific cases such as XHR post requests, a full CAPTCHA page render might not be an option. In such cases, the Advanced Blocking Response (ABR) returns a JSON object containing all the information needed to render a customized CAPTCHA challenge implementation such as a popup modal, a section on the page, etc. This provides more flexibility and customizability in displaying the CAPTCHA challenge.

• true: Enable ABR
• false: Disable ABR

Activates the full blocking flow to verify the flow works as expected if a particular header is present on the request. Often used during monitor mode, where the Enforcer collects data without blocking user requests, before switching to active_blocking.

Whether to enable the extraction and reporting of credentials from the Enforcer for Credential Intelligence.

• true: Enable Credential Intelligence
• false: Disable Credential Intelligence

An array of configuration objects for each credential endpoint. Each element in the array is an object representing a distinct endpoint to which credentials are sent and includes:

• How to identify these credential-bearing requests
• How to extract the credentials from the request
• How to determine if the request operation (login, signup, etc.) was successful based on the returned HTTP response

Click to expand the full properties list.

1
{
2
    // ...
3
    path: '/sign-up',
4
    // ...
5
}

1
{
2
    // ...
3
    path: '/auth/[A-Za-z0-9]{12}/login',
4
    path_type: 'regex',
5
    // ...
6
}

1
{
2
    // ...
3
    method: 'POST',
4
    // ...
5
}

1
{
2
    // ...
3
    sent_through: 'body',
4
    // ...
5
}

1
{
2
    // ...
3
    sent_through: 'body',
4
    user_field: 'username',
5
    // ...
6
}

1
{
2
    // ...
3
    sent_through: 'body',
4
    user_field: 'username',
5
    // ...
6
}

1
{
2
    // ...
3
    protocol: 'v2',
4
    // ...
5
}

1
{
2
    // ...
3
    login_successful_reporting_method: 'status',
4
    // ...
5
}

1
{
2
    // ...
3
    login_successful_reporting_method: 'status',
4
    login_successful_statuses: [200, 202],
5
    // ...
6
}

1
{
2
    // ...
3
    login_successful_reporting_method: 'body',
4
    login_successful_body_regex: 'Welcome, [A-Za-z0-9_]+!'
5
    // ...
6
}

1
{
2
    // ...
3
    login_successful_reporting_method: 'header',
4
    login_successful_header_name: 'x-login-successful'
5
    // ...
6
}

1
{
2
    // ...
3
    login_successful_reporting_method: 'header',
4
    login_successful_header_name: 'x-user-status',
5
    login_successful_header_value: 'logged-in'
6
    // ...
7
}

The header name to be set on the incoming request if the credentials are compromised. If this header is added, its value will always be 1. If credentials have not been identified as compromised, the header will not be added to the request.

Whether to attach the additional_s2s payload and URL as headers to the original request. This is done so that the additional_s2s activity can be enriched with the proper login_successful value and sent to the provided URL at a later stage. Enabling this configuration disables automatic sending of additional_s2s activity.

When set to true, the following headers are added to the origin request:

• px-additional-activity: A JSON object containing the payload of the additional_s2s activity. The login_successful and http_status_code fields should be set prior to sending the activity.
• px-additional-activity-url: The URL to which the additional_s2s payload should be sent as an HTTP POST request.

1
app.post('/login', (req, res) => {
2
    // handle login flow, resulting in variables
3
    // isLoginSuccessful (boolean) and responseStatusCode (number)
4
5
    if (
6
        req.headers['px-additional-activity'] &&
7
        req.headers['px-additional-activity-url']
8
    ) {
9
        handlePxAdditionalActivity(req, responseStatusCode, isLoginSuccessful);
10
    }
11
});
12
13
function handlePxAdditionalActivity(req, statusCode, isLoginSuccessful) {
14
    try {
15
        // extract url and activity from the request headers
16
        const url = req.headers['px-additional-activity-url'];
17
        const activity = JSON.parse(req.headers['px-additional-activity']);
18
19
        // enrich the activity details with added information
20
        activity.details['http_status_code'] = statusCode;
21
        activity.details['login_successful'] = isLoginSuccessful;
22
23
        if (activity.details['credentials_compromised'] && isLoginSuccessful) {
24
            // add raw username if credentials are compromised and login is successful (only if desired)
25
            activity.details['raw_username'] = req.body.username;
26
        } else {
27
            // remove raw username if login is not successful or credentials are not compromised
28
            delete activity.details['raw_username'];
29
        }
30
31
        // send the POST request
32
        axios.post(url, activity, {
33
            headers: {
34
                'Authorization': `Bearer ${env.PX_AUTH_TOKEN}`,
35
                'Content-Type': 'application/json'
36
            }
37
        });
38
    } catch (err) {
39
        console.error(`Error: ${err}`);
40
    }
41
}

Whether to report the raw username on the additional_s2s activity.

• false: The raw username will never be reported.
• true: The raw username will only be reported if:
  • The credentials are compromised, and
  • The login request was successful.

The default login-success detection method applied to endpoints that don’t override it. See login_successful_reporting_method for the possible values.

The default HTTP status codes that indicate a successful login. This takes effect when the PX_CI_LS_REPORTING_METHOD is set to status.

The default body regular expression that indicates a successful login. This takes effect when the PX_CI_LS_REPORTING_METHOD is set to body.

The default response header name that indicates a successful login. This takes effect when the PX_CI_LS_REPORTING_METHOD is set to header.

The default response header value that indicates a successful login. This takes effect when the PX_CI_LS_REPORTING_METHOD is set to header.

The default credential hashing protocol applied to endpoints that do not specify a protocol field.

• "v2": Both username and password are present on the same HTTP request and must be extracted successfully to trigger Credential Intelligence.
• "multistep_sso": The username and password are delivered on different HTTP requests. Either the username or password, but not both, must be extracted successfully to trigger Credential Intelligence.
• "both": The username and password may be present on the same HTTP request or on different HTTP requests. If either username or password is successfully extracted, the Enforcer will send the credentials according to the multistep_sso protocol. If both username and password are successfully extracted, the Enforcer will send the credentials according to the v2 protocol.

Whether to enable CORS support.

• true: Enable CORS support
• false: Disable CORS support

After setting this configuration to true, the Enforcer:

• Automatically adds the following default CORS response headers to block responses resulting from CORS requests.

  Access-Control-Allow-Origin: <ORIGIN_REQUEST_HEADER_VALUE>  
  Access-Control-Allow-Credentials: true
• Activates the px_cors_create_custom_block_response_headers configuration, which lets you customize the block response headers via a custom function.

By default, the Enforcer extracts HUMAN cookies from the Cookie header. However, if these cookies are transferred on a different header, then that header’s name must be provided with this configuration.

Routes or prefixes that should be enforced by HUMAN even when the Enforcer is in monitor mode.

Routes must be configured as a single regular expression (RegExp). For case-insensitive matching, the end the regex with the i flag.

Filters out requests with the specified file extension. By default, HUMAN doesn’t enforce static assets such as images and documents to minimize unncessary API calls and computation, but you can configure this list at any time.

Configure as a comma-separated list.

Filters out requests with the specified HTTP method to avoid unnecessary traffic in the Enforcer verification flow. Configure as a comma-separated list.

Filters out requests with the specified IP address to avoid unnecessary traffic in the Enforcer verification flow. Configure IPs or CIDR ranges as a comma-separated list (for example, 1.1.1.1,2.2.2.2/8).

Filters out requests with the specified route to avoid unnecessary traffic in the Enforcer verification flow. Requests to these specified routes will never be blocked regardless of their risk score and will never generate risk or async activities. Routes must be configured as a single regular expression (RegExp). For case-insensitive matching, the end the regex with the i flag (for example, /^(./allowed_route/?.)|(./filtered_route/?.)$/i).

Filters out requests with the specified user agent to avoid unnecessary traffic in the Enforcer verification flow. User agents must be configured as a single regular expression (RegExp). For case-insensitive matching, the end the regex with the i flag (for example, /^(filtered-ua)|(filtered-user-agent)$/).

Whether to enable first party mode for Bot Defender or Sightline Cyberfraud Defense.

Whether to parse and report information about GraphQL operations on incoming requests. When true, all POST requests with routes that match the prefixes configured in PX_GRAPHQL_ROUTES will have their bodies parsed for GraphQL operations.

• true: Enable GraphQL support
• false: Disable GraphQL support

A regular expression that matches all routes that should be considered GraphQL routes. If PX_GRAPHQL_ENABLED is true, all POST requests with routes that match the configured regex will have their bodies parsed for GraphQL operations. For case-insensitive matching, the regex should end with the i flag.

A regular expression (RegExp) of operation names that should be considered sensitive. Some routes may be more prone to bot attacks than others, such as routes that execute payments or handle personal information. You can configure these routes as sensitive to ensure a more stringent protection.

If one or more GraphQL operations has a name or keyword matching this regular expression (RegExp), the Enforcer will trigger a Risk API call even if the request contains a valid, unexpired cookie. Matches against extracted GraphQL words from:

• PX_GRAPHQL_KEYWORDS configuration
• px_extract_graphql_keywords configuration

For case-insensitive matching, the regex should end with the i flag. For example, /^(LoginOperation|SignIn)$/i.

A comma-separated list of operation types that should be considered sensitive. Some routes may be more prone to bot attacks than others, such as routes that execute payments or handle personal information. You can configure these routes as sensitive to ensure a more stringent protection.

If one or more GraphQL operations on an HTTP request has a type matching this list, the Enforcer will trigger a Risk API call even if the request contains a valid, unexpired cookie.

A regular expression (RegExp) of keywords to identify important terms from GraphQL operation queries. These keywords are used to determine the purpose of the operation (such as login, checkout, or search) and can also be used to specify which operations should be considered sensitive. Any matching patterns will be extracted and reported to HUMAN. See PX_SENSITIVE_GQL_OP_NAMES for more information. See px_extract_graphql_keywords for an alternative using a custom function.

For case-insensitive matching, the regex should end with the i flag. For example, /(\w*[Ll]ogin\w*)|(\w*[Ss]ignup\w*)/i.

Adds a header to the incoming request with the configured header name and the JSON-stringified data enrichment object as the value. If empty or if data enrichment has not been enabled for your policy, no header will be set. To view available data and enable this feature, see Data classification enrichment.

A way to include a custom CSS file to the block page.

For example, https://www.example.com/custom/style.css.

A way to include custom JavaScript to the block page. This script will run after the default JavaScript scripts.

For example, https://www.example.com/custom_script.js.

Adds a custom logo to the HUMAN Challenge block page via URL.

For example, https://www.example.com/custom_logo.png.

A regular expression (RegExp) of endpoints to be monitored rather than blocked by the Enforcer, even when the Enforcer is in active_blocking mode. For case-insensitive matching, the regex should end with the i flag. For example, /^(./category/?.)|(./product/?.)$/i.

The PX Hashed Data (PXHD) cookie links the first risk request with the browser activities as detected by the Sensor for better user tracking. It can also add more information that’s shared between the HUMAN Collector, Enforcer, and Sensor. This configuration determines whether the Secure cookie attribute is added when setting the PXHD cookie.

See Use of cookies & web storage for more information.

• true: Adds the Secure attribute to the PXHD cookie
• false: Does not add the Secure attribute to the PXHD cookie

An alternative to the basic logger configuration. This sends Enforcer logs to HUMAN’s logging service if a specific header is present on the request. This is particularly useful for expedited debugging, diagnosis, and resolution of any integration or Enforcer-related issues.

Contact HUMAN to recieve your token.

Security Settings: Hidden

The token used to authenticate the Enforcer with the HUMAN Remote Configuration service.

Contact HUMAN to receive your token. Security Settings: Hidden

The ID associated with the Remote Configuration.

Contact HUMAN to receive your ID.

The maximum number of time to attempt to fetch the Remote Configuration. If the Enforcer fails to fetch the Remote Configuration after the specified maximum, it will use the last known configuration.

The interval time in milliseconds to wait between attempts to fetch the Remote Configuration.

Specifies certain headers that should not be forwarded to any other destination, including the HUMAN Detector. While HUMAN’s detection system will continue to use these headers to determine whether to block or not, the specified headers won’t be forwarded from the Enforcer, won’t appear in Enforcer activities, and won’t be sent to any other IP if the Enforcer acts as a proxy. Should be configured as a comma-separated list of header names.

A regular expression (RegExp) of prefixes for all routes that should be considered sensitive.

For case-insensitive matching, the regex should end with the i flag. For example, /^(/login/.*)|(/sign/)$/i.

When true, the Enforcer will decode reserved characters such as %3F and %2F in the request URL path prior to processing. In other words, the Enforcer will treat the URIs /login%3F.ico and /login?.ico as equivalent. By default, the Enforcer doesn’t decode reserved characters and treats these URLs separately.

• true: Decode reserved characters in the request URL.
• false: Do not decode reserved characters in the request URL.

The name of the cookie that contains the JWT token that HUMAN should extract user identifiers from. For example, auth.

The field name in the JWT object, extracted from the JWT cookie, that contains the user ID to be extracted and reported. For example, nameID.

The field names in the JWT object, extracted from the JWT cookie, that should be extracted and reported in addition to the user ID. The field names should be configured as a comma-separated list. For example, exp,iss.

The name of the header that contains the JWT token that HUMAN should extract user identifiers from. For example, x-jwt-authorization.

The field name in the JWT object, extracted from the JWT header, that contains the user ID to be extracted and reported. For example, sub.

The field names in the JWT object, extracted from the JWT header, that should be extracted and reported in addition to the user ID. The field names should be configured as a comma-separated list. For example, exp,iss.

A custom function passed to the Enforcer that runs after sending page_requested or block activity to the Collector and before forwarding the request to the next step in the pipeline. A common use case is to set the score as a variable or header. Then the application can read the score and do what is defined within the application’s logic.

Parameters:

• config: HumanSecurityConfiguration
• context: IContext
• request: EW.IngressClientRequest | EW.ResponseProviderRequest

Returns: void or a Promise resolving to void

1
const config: HumanSecurityFunctionsConfiguration = {
2
    // ...
3
    px_additional_activity_handler: (
4
        config: HumanSecurityConfiguration,
5
        context: IContext,
6
        request: EW.IngressClientRequest | EW.ResponseProviderRequest
7
    ): void => {
8
        if ('setHeader' in request) {
9
            request.setHeader('x-px-score', `${context.score}`);
10
            request.setHeader('x-px-rtt', `${context.riskApiData.riskRtt}`);
11
        }
12
    },
13
    // ...
14
}

If the default CORS response headers are not sufficient, you can use this configuration to customize the headers that should be added to all block responses resulting from CORS requests. If this function is defined, the default headers will not be added. Only those headers specified in the returned object will be added to the block response.

Parameters:

• request: EW.IngressClientRequest | EW.ResponseProviderRequest

Returns: An object of the type Record<string, string[]> or a Promise resolving to this type

1
const config: HumanSecurityFunctionsConfiguration = {
2
    // ...
3
    px_cors_create_custom_block_response_headers: (
4
        request: EW.IngressClientRequest | EW.ResponseProviderRequest,
5
    ): Record<string, string[]> => {
6
        return {
7
            'Access-Control-Allow-Origin': [request.getHeader('origin')?.[0] ?? '*'],
8
            'Access-Control-Allow-Credentials': ['false'],
9
            'Access-Control-Allow-Methods': ['GET', 'POST', 'PUT'],
10
            'X-Custom-Header': ['1']
11
        };
12
    },
13
    // ...
14
}

Required if sent_through is set to "custom". A custom credential extraction callback that returns the raw credentials from the request. It receives the HTTP request as a parameter and should return a Credentials object:

1
type Credentials = {
2
    user?: string;  // the raw username
3
    pass?: string;  // the raw password
4
};

Parameters:

• request: EW.ResponseProviderRequest

Returns: A Credentials object or a Promise resolving to a Credentials object. If neither the username or the password can be extracted from the request, the function should return null.

1
{
2
    // ...
3
    sent_through: 'custom',
4
    extract_credentials_callback: async (request: EW.ResponseProviderRequest): Promise<{ user?: string; pass?: string; }> => {
5
        const body: string | undefined = await HumanSecurityUtils.getRequestBody(request);
6
        
7
        // custom logic to extract credentials from the request body
8
        
9
        if (!username || !password) {
10
            return null;
11
        }
12
        return { user: username, pass: password };
13
    },
14
    // ...
15
}

Required if login_successful_reporting_method is set to "custom". A custom callback that accepts the HTTP response and returns a boolean or Promise resolving to a boolean that indicates whether the login attempt was successful.

Parameters:

• response: { status: number; headers: Record<string, string[]>; body: any }

Returns: A boolean or a Promise resolving to a boolean.

1
{
2
    // ...
3
    login_successful_reporting_method: 'custom',
4
    login_successful_callback: async (response: { status: number; headers: Record<string, string[]>; body: any }): Promise<boolean> => {
5
        return response.status === 200 
6
                && response.headers['set-cookie']?.some((val) => val.includes('session_token='))
7
                && await HumanSecurityUtils.getResponseBody(response).includes('Welcome!');
8
    },
9
    // ...
10
}

Enriches activities sent from the Enforcer to HUMAN with additional custom parameters. This data can include user information, session IDs, or other data that HUMAN should have access to. These custom parameters are defined by a configurable function that must return an object that contains these custom parameters. There is a limit of 10 custom parameters.

Parameters:

• config: HumanSecurityConfiguration
• request: EW.IngressClientRequest | EW.ResponseProviderRequest

Returns: Promise<CustomParameters>

1
const config: HumanSecurityFunctionsConfiguration = {
2
    // ...
3
    px_enrich_custom_parameters: async (
4
        config: HumanSecurityConfiguration,
5
        request: EW.IngressClientRequest | EW.ResponseProviderRequest,
6
    ): CustomParameters | Promise<CustomParameters> => {
7
        let body = null;
8
        if ('body' in request && request.method === 'POST') {
9
            try {
10
                body = JSON.parse(await HumanSecurityUtils.getRequestBody(request))
11
            } catch {
12
                // fail silently
13
            }
14
        }
15
        return {
16
            custom_param1: 'hardcoded value',
17
            custom_param2: request.getHeader('header-name'),
18
            custom_param3: body?.['body_property']
19
        };
20
    },
21
    // ...
22
}

A custom function that lets you define which requests should be enforced based on custom logic. It accepts the incoming request as an argument and returns a boolean indicating whether the request should be enforced.

Parameters:

• request: EW.IngressClientRequest | EW.ResponseProviderRequest

Returns: A boolean or a Promise resolving to a boolean.

1
const config: HumanSecurityFunctionsConfiguration = {
2
    // ...
3
    px_custom_is_enforced_request: (request: EW.IngressClientRequest | EW.ResponseProviderRequest): boolean | Promise<boolean> => {
4
        return request.method === 'POST' && request.path.startsWith('/enforced_route');
5
    },
6
    // ...
7
}

A custom function that lets you define which requests should be filtered based on custom logic. It accepts the incoming request as an argument and returns a boolean indicating whether the request should be filtered.

Parameters:

• request: EW.IngressClientRequest | EW.ResponseProviderRequest

Returns: A boolean or a Promise resolving to a boolean.

1
const config: HumanSecurityFunctionsConfiguration = {
2
    // ...
3
    px_custom_is_filtered_request: (request: EW.IngressClientRequest | EW.ResponseProviderRequest): boolean | Promise<boolean> => {
4
        return request.method === 'GET' && request.path.startsWith('/static/');
5
    },
6
    // ...
7
}

A custom function that identifies key terms from GraphQL operation queries. An alternative to the PX_GRAPHQL_KEYWORDS configuration.

This function accepts the GraphQL query string and must return an array of strings representing all keywords found in the query. These keywords are used to determine the purpose of the operation (such as login, checkout, search) and can also be used to specify which GraphQL operations should be considered sensitive. See PX_SENSITIVE_GQL_OP_NAMES for more information.

If this function is defined and returns an array (even an empty array), then the returned array will be used as the GraphQL keywords. If this function is defined and returns null, then the query will continue to be evaluated using PX_GRAPHQL_KEYWORDS.

Parameters:

• graphqlQuery: string

Returns string[] or a Promise resolving to string[].

1
const config: HumanSecurityFunctionsConfiguration = {
2
    // ...
3
    px_extract_graphql_keywords: (graphqlQuery: string): string[] | Promise<string[]> => {
4
        if (/userId\d+/.test(graphqlQuery)) {
5
            // report no keywords for this query
6
            return [];
7
        } else if (/perform(Login|Signin)/.test(graphqlQuery)) {
8
            // always report 'login' as the only keyword for this query
9
            return ['login'];
10
        } else {
11
            // process query according to px_graphql_keywords configuration
12
            return null;
13
        }
14
    },
15
    // ...
16
}

A custom function that lets you define which endpoints should be monitored based on custom logic. It accepts the incoming request as an argument and returns a boolean indicating whether the request should be monitored.

Parameters:

• request: EW.IngressClientRequest | EW.ResponseProviderRequest

Returns: A boolean or a Promise resolving to a boolean.

1
const config: HumanSecurityFunctionsConfiguration = {
2
    // ...
3
    px_custom_is_monitored_request: (request: EW.IngressClientRequest | EW.ResponseProviderRequest): boolean | Promise<boolean> => {
4
        return request.method === 'GET' && request.path.startsWith('/monitored');
5
    },
6
    // ...
7
}

A function that receives the configuration and the response from the origin and returns up to ten fields: custom_param11 through custom_param20. These are merged into page_requested, additional_s2s, and simulated block activities. There is a limit of ten response custom parameters.

Parameters:

• config: HumanSecurityConfiguration
• response: { status: number; headers: Record<string, string[]>; body: any }

Returns: An object with custom_param11–custom_param20 keys, or a Promise resolving to that object.

1
const config: HumanSecurityFunctionsConfiguration = {
2
    // ...
3
    px_enrich_response_custom_parameters: async (
4
        config: HumanSecurityConfiguration,
5
        response: { status: number; headers: Record<string, string[]>; body: any },
6
        request?: EW.ResponseProviderRequest | EW.IngressClientRequest,
7
    ): Promise<Record<string, string>> => {
8
        const bodyText = await HumanSecurityUtils.getResponseBody(response);
9
        return {
10
            custom_param11: response.headers['x-request-id']?.[0] ?? '',
11
            custom_param12: String(response.status),
12
            custom_param13: request?.getHeader('user-agent')?.[0] ?? '',
13
            custom_param14: bodyText?.includes('success') ? 'true' : 'false',
14
            // ... up to custom_param20
15
        };
16
    },
17
    // ...
18
}

A custom function that lets you define which requests should be considered sensitive based on custom logic. It accepts the incoming request as an argument and returns a boolean indicating whether the request should be considered sensitive.

Parameters:

• request: EW.IngressClientRequest | EW.ResponseProviderRequest

Returns: A boolean or a Promise resolving to a boolean.

1
const config: HumanSecurityFunctionsConfiguration = {
2
    // ...
3
    px_custom_is_sensitive_request: (request: EW.IngressClientRequest | EW.ResponseProviderRequest): boolean | Promise<boolean> => {
4
        return request.method === 'POST' || request.method === 'PUT';
5
    },
6
    // ...
7
}