Configure the Virtual Waiting Room behavior (Visitor Prioritization Cloudlet with FIFO) in Property Manager

In Property Manager, behaviors apply certain features to your configuration. Behaviors help shape how requests passing through the ​Akamai​ network are handled and processed.

📘

Virtual Waiting Room and Visitor Prioritization cloudlets use different Property Manager behaviors.

  • The Visitor Prioritization Cloudlet with FIFO behavior is used with the Virtual Waiting Room cloudlet.
  • The Visitor Prioritization behavior is used with the Visitor Prioritization cloudlet.

Visitor Prioritization Cloudlet with FIFO and Visitor Prioritization behaviors can not be used together on the same property version.

How to

  1. 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.

  2. Select the property and version you want to add your Cloudlet to.

  3. Click Add Rule, then select Blank Rule Template from the menu.

  4. Give the new rule a name and click Insert Rule.
    The Criteria, and Behaviors templates are added.

  5. Click Add Match and add match criteria. Repeat this step to add additional match criteria if required.
    Example.

  6. Click Add Behavior, and search for and select Visitor Prioritization Cloudlet with FIFO.

  7. Click Insert Behavior. Refer to the following table to complete the fields.

Field

Action

FIFO Policy (required)

Select an existing Visitor Prioritization FIFO policy to use with this behavior. The list contains only shared policies.

Domain

The domain for establishing a visitor session.
Incoming Host Header (Automatic) for basic domain auto detection or
Custom (Advanced Settings) for advanced configuration.

Cookie Domain Override

The advanced option to set a custom domain attribute for all session cookies. This option is available when Domain is set to Custom (Advanced Settings). Make sure this domain is correctly accepted by the user agent for any request matching with this behavior. When multiple property hostnames are configured, the cookie domain is the common domain. Do not use only the top level domains (TLDs) for the cookie domain.
This option supports variable expression syntax. Typing {{ in the option field triggers variable autocomplete. To learn more about variable support, see CSH lookup.

Waiting Room

Path

The path to the waiting room main page on the Origin. For blocked requests when the Origin reaches its limit, the outgoing request path and cache key is rewritten to this path value as waiting room main page requests. The waiting room path is not visible to visitors.
You can use match criteria to further customize the behaviors for Waiting Room Requests.
This option supports variable expression syntax. Typing {{ in the option field triggers variable autocomplete. To learn more variable support, see CSH lookup.

Assets

Base path for waiting room assets such as; javascript, css files and images that are referenced in the waiting room HTML. e.g. /static/*. Each path may contain an asterisk (*) for wildcards. Requests matching with any of these paths are not blocked, but marked as Waiting Room Assets requests and passed through to the Origin.
You can use match criteria to further customize the behaviors for Waiting Room Assets.

Granting Access

Duration

Define how long access should be granted (in seconds) for inactive visitors at the origin.
- If the duration expires and there are visitors in your waiting room, the visitor is sent to the end of the waiting room line.
- If the duration expires and there are no visitors in your waiting room, the duration is reset and the visitor is allowed to stay on the origin.

0 through 86400 seconds
Note: 24 hours (86400 seconds) is the maximum duration.

Auto Extend

Set the toggle to On if the access should be prolonged automatically when the visitor is active.

  1. Click Save.

Did this page help you?