Admin Guide › Security Profiles › Content Acl

Content ACL

Navigation: Security Profiles

Match request headers, hostnames, URI values, or GEOIP and apply allow, drop, or block actions.

Content ACL

Add / Edit forms

Click + Add New to open the creation dialog, or Edit on an existing row to modify a record.

List view

List view

Add form — all tabs

The add dialog contains 2 tabs. Example values in the filled screenshots are for documentation only — do not save them on a production appliance.

General

Field Required Description Example Why this data is needed
Profile Name Yes Unique name for proxy rule attachment. API_ACL Required — proxy rules select this profile by name.
Default Action Yes Allow or deny when no ACL rule matches. Deny Required — secure default is Deny (whitelist approach).
Status Yes Enable or disable this profile. Enabled Must be Enabled for ACL rules to take effect.

Empty:

Add — General (empty)

Filled with example data (for illustration — shows why each field needs a value):

Add — General (filled)

ACL Rules

Field Required Description Example Why this data is needed
URI Pattern Yes Path or regex to match (e.g. /api/*). /api/v1/* Required — defines which URLs this ACL entry controls.
HTTP Method No GET, POST, PUT, DELETE, or any. GET Optional — restrict rule to specific HTTP methods.
Action Yes Allow or deny matched requests. Allow Required — determines whether matching traffic passes.

Empty:

Add — ACL Rules (empty)

Filled with example data (for illustration — shows why each field needs a value):

Add — ACL Rules (filled)

Edit form — all tabs

The edit dialog contains 2 tabs. Fields are the same as Add — values show the currently saved record:

General

Field Required Description Example Why this data is needed
Profile Name Yes Unique name for proxy rule attachment. API_ACL Required — proxy rules select this profile by name.
Default Action Yes Allow or deny when no ACL rule matches. Deny Required — secure default is Deny (whitelist approach).
Status Yes Enable or disable this profile. Enabled Must be Enabled for ACL rules to take effect.

Edit — General

ACL Rules

Field Required Description Example Why this data is needed
URI Pattern Yes Path or regex to match (e.g. /api/*). /api/v1/* Required — defines which URLs this ACL entry controls.
HTTP Method No GET, POST, PUT, DELETE, or any. GET Optional — restrict rule to specific HTTP methods.
Action Yes Allow or deny matched requests. Allow Required — determines whether matching traffic passes.

Edit — ACL Rules

Page sections

Available actions

Table columns

Tabs