Manual Chapter : Configuring a per-request policy for an HTTP Connector

Applies To:

Show Versions Show Versions

BIG-IP APM

  • 15.1.0
Manual Chapter

Configuring a per-request policy for an HTTP Connector

You must have an HTTP Connector Request configured to add the HTTP Connector in a per-request policy.
Add and configure the HTTP Connector to a per-request policy to run a check against an external server. In this example, you check whether an IP address is listed on a blocklist (in this scenario, the Neutrino API blocklist).
  1. On the Main tab, click
    Access
    Profiles / Policies
    Per-Request Policies
    .
    The Per-Request Policies screen opens.
  2. To create a new per-request policy, click
    Create
    , type a name that is unique among all access profiles and per-request policies, select the accepted languages, and click
    Finished
    .
    The Per-Request Policies screen displays the new per-request policy.
  3. In the
    Name
    field, locate the policy that you want to update, then in the
    Per-Request Policy
    field, click the
    Edit
    link.
    The visual policy editor opens in another tab.
  4. Click the
    Add New Subroutine
    button.
    A popup screen opens.
  5. Type a
    Name
    for the new subroutine.
    For example, because this subroutine checks the IP address against a blocklist, you can specify the name
    Check Blocklist
    .
  6. On the
    Select Subroutine template
    list, retain the selection
    Empty
    , and click
    Save
    .
    The popup screen closes. The subroutine, with the heading
    [+] Subroutine:
    Name
    , displays below the main editor.