You can use a per-request policy to protect your internal resources and to be more selective about who accesses them and when. After a user starts a session, a per-request policy makes it possible to apply additional criteria for access any time the user makes a request. These steps are for use in a reverse proxy configuration; that is, with APM® and LTM® set up for web access management.
To add per-request processing to a configuration, associate the per-request policy with the virtual server.
Each URL Filter Assign item in this per-request policy example should specify a filter that is applicable to the user group.
URL filter based on group membership
This per-request policy example applies specific URL filters for weekends and weeknights, and restricts access during work hours based on user group.
Deny or allow access based on date and time and group membership
In this per-request policy example, only recruiters are allowed to access URLs in the user-defined category Employment. The policy also restricts access to entertaining videos during business hours.
Category-specific access restrictions (using user-defined categories)
Application access control by application family, application name, and application filter
|1||A user-defined branch for the instant messaging application family.|
|2||A user-defined branch for a specific application.|
|3||The default fallback branch, on which an application filter is applied. Application Filter Assign needs the information provided by Application Lookup.|