Applies To:Show Versions
- 17.0.0, 16.1.2, 16.1.1, 16.1.0
Configuring a per-request policy to select the next hop
- On the Main tab, click.The Per-Request Policies screen opens.
- To create a new per-request policy, clickCreate, type a name that is unique among all access profiles and per-request policies, select the accepted languages, and clickFinished.The Per-Request Policies screen displays the new per-request policy.
- In theNamefield, locate the policy that you want to update, then in thePer-Request Policyfield, click theEditlink.The visual policy editor opens in another tab.
- On a policy branch, click the(+)icon to add an item to the policy.The actions you can use for building a per-request policy are displayed on a popup screen with actions on tabs, such as Authentication, Classification, and General Purpose, and a search field.
- On the Traffic Management tab, selectProxy Selectand clickAdd Item.A Properties popup screen opens.
- From thePoollist, select a pool of one or more proxy servers to serve as the next hop.All proxy servers in the pool that you select must support the forward proxy mode that you specify in theUpstream Proxy Modesetting.
- FromUpstream Proxy Mode, select:
- Explicitif the proxy servers in the pool support explicit forward proxy.
- Transparentif the proxy servers in the pool support transparent forward proxy.
- ForUsernameandPassword, most of the time you can retain the default values (blank).These fields support the use of static credentials to authenticate the user at the next hop using HTTP Basic authentication.
- ClickSave.The properties screen closes. The visual policy editor displays.