Configure the Visitor Prioritization behavior
In Property Manager, behaviors apply certain features to your configuration. Behaviors help shape how requests passing through the Akamai network are handled and processed.
How to
-
Access Property Manager configurations associated with the selected Akamai Control Center account. Go to ☰ > CDN > Properties (or just enter Properties in the search box).
The Property Groups page opens.
-
Select the property and version you want to add your Cloudlet to.
-
Click Add Behavior, then select Visitor Prioritization.
-
Complete the following fields:
| Field | Action |
|---|---|
| Standard Fields | |
| Enable | Set to On. |
| Policy Name | Select an existing Visitor Prioritization policy to use with this behavior. You create policies in Cloudlets Policy Manager. |
| User Identification | |
| By Cookie Value | Set to On to identify users by the value of a cookie. |
| Cookie Name | If identifying users by a cookie value, enter the name of the cookie with the value you want to use. User identification occurs when the value of the cookie is the same across all requests. |
| By Request Headers | Enable to identify users by specific parameters from either GET or POST requests. |
| Headers | If identifying users by request headers, enter one or more request headers. User identification occurs when the header values are the same across all requests. If using multiple headers, all have to match to identify a user. |
| By IP Address | Enable to identify users by their IP address. |
| By Request Parameters | Enable to identify users by specific request parameters. Depending on the request method, these will be either GET or POST parameters. |
| Parameters | If identifying users by request parameters, enter one or more request parameters. User identification occurs when the value of the parameters listed is the same across all requests. The value can be absent or blank. If using multiple parameters, all have to match to identify a user. |
| Allowed User Cookie Management | |
| Enable | Select whether to enable the Allowed User Cookie, which is set once a user has been allowed through to the site. |
| Instance Label | Enter the label to use to distinguish this Allowed User Cookie from others. This value impacts the cookie's name. It lets you have a single allowed user assignment across multiple digital properties. If you want to also include a cookie domain, enable Advanced Settings and specify the Domain option. |
| Allowed User Duration (sec) | Select the duration of the Allowed User Cookie. Once a user is allowed into the site, this cookie bypasses Visitor Prioritization for subsequent requests. |
| Extend Membership | Selecting Yes enables Extend Membership. Extend membership allows visitors to access the site and bypass the waiting room as long as they remain active during the Allowed User Duration (sec) period. For example, if Extend Membership is enabled and Allowed User Duration (sec) is set to 5 minutes (300 seconds), and the visitor makes subsequent requests within 5 minutes of each other; - the visitor gets access to the site and bypasses the waiting room. - the cookie continuously renews. - the cookie expiry continuously resets to 5 minutes into the future, thus creating a rolling window. If the same visitor fails to initiate a request within 5 minutes, then their next request is subject to the Visitor Prioritization logic that you defined which may include sending the visitor to the waiting room. Selecting No allows visitors to bypass the waiting room only for the fixed amount of time set in Allowed User Duration (sec). After the Allowed User Duration (sec) time lapses, the visitor is subject to the Visitor Prioritization logic that you defined. Selecting Send All to Waiting Room in the Visitor Prioritization rule in Cloudlets Policy Manager overrides your settings in this field. |
| Advanced Settings | Select whether to display advanced configuration settings for the Allowed User Cookie. |
| Automatic Salt | If Advanced Settings are enabled, select whether to automatically set a salt for the cookie. This salt helps verify the integrity of the Allowed User Cookie. You may not want to use this setting if you intend to share the cookie across several digital properties. |
| Salt | If Advanced Settings is enabled and Automatic Salt is disabled, enter the salt string to use to verify the Allowed User Cookie's integrity. This value is encoded into the cookie's value to prevent manipulation by the user. If you use the same salt string in different Visitor Prioritization behaviors, the Allowed User Cookie can provide access to multiple instances of the Visitor Prioritization Cloudlet. |
| Domain Type | Select whether to use the incoming host header or a custom cookie domain with the Allowed User Cookie. |
| Domain | If you're using a custom domain type, enter the cookie domain to use for the Allowed User Cookie. |
| Set HttpOnly Flag | If Advanced Settings is enabled, select whether to set the HttpOnly flag for the Allowed User Cookie. When enabled, the user agent only makes the cookie available for true HTTP requests. |
| Waiting Room Cookie Management | |
| Enable | Select whether to enable Waiting Room Cookie, which holds users in the waiting room. This cookie sends users back to the waiting room if they refresh the waiting room page. |
| Share Label | If the Allowed User Cookie is enabled, select to share the Instance Label from your Allowed User Cookie. If disabled, specify a different instance label. |
| Waiting Room Duration (sec) | Select the duration in seconds for the Waiting Room Cookie. |
| Advanced Settings | Select whether to display advanced configuration settings for the Waiting Room Cookie. |
| Automatic Salt | If Advanced Settings is enabled, select whether to select a salt for the cookie automatically. This salt is used to verify the integrity of the Waiting Room Cookie. You may not want to use this setting if you intend to share the cookie across several digital properties. |
| Salt | If Advanced Settings is enabled and Automatic Salt isn't, enter the salt to use to verify the Waiting Room Cookie's integrity. This value is encoded into the cookie's value to prevent manipulation by the user. |
| Domain Type | Select whether to use the incoming host header or a customer cookie domain with the Waiting Room Cookie. |
| Domain | If Advanced Settings is enabled, enter the cookie domain to use for the Waiting Room Cookie. |
| Set HttpOnly Flag | If Advanced Settings is enabled, select whether to set the HttpOnly flag for the Waiting Room Cookie. When enabled, the user agent will only make the cookie available for true HTTP requests. |
| Waiting Room Management | |
| HTTP Status Code | Select the HTTP response code served for requests sent to the waiting room. Options include 200 (OK), and 503 (Service Unavailable). |
| Track with CP Code | Set to On to use a Content Provider (CP) code to track requests sent to the waiting room. |
| CP Code | If Track with CP Code is enabled, either enter an existing CP code or create a new one to track requests sent to the waiting room. |
| NetStorage | Choose the NetStorage domain that contains the waiting room page. |
| Directory | Enter the directory within the selected NetStorage domain that contains the static waiting room page. Do not include the vp directory or the trailing slash in the path. |
| Cache TTL (min) | Select a time between 5 and 30 minutes that the waiting room page will reside in cache. This time period is known as the time to live (TTL) The default is five minutes. |
-
Click Save.
-
Activate the newly updated property.
Updated over 1 year ago