Get Waiting Rooms Result
Constructors
Properties
Only available for the Waiting Room Advanced subscription. Additional hostname and path combinations to which this waiting room will be applied. There is an implied wildcard at the end of the path. The hostname and path combination must be unique to this and all other waiting rooms.
Configures cookie attributes for the waiting room cookie. This encrypted cookie stores a user's status in the waiting room, such as queue position.
Appends a '' + a custom suffix to the end of Cloudflare Waiting Room's cookie name(cfwaitingroom). If cookie_suffix
is "abcd", the cookie name will be __cf_waitingroom_abcd
. This field is required if using additional_routes
.
Only available for the Waiting Room Advanced subscription. This is a template html file that will be rendered at the edge. If no custompagehtml is provided, the default waiting room will be used. The template is based on mustache ( https://mustache.github.io/ ). There are several variables that are evaluated by the Cloudflare edge:
The language of the default page template. If no default_template_language is provided, then en-US
(English) will be used. Available values: "en-US", "es-ES", "de-DE", "fr-FR", "it-IT", "ja-JP", "ko-KR", "pt-BR", "zh-CN", "zh-TW", "nl-NL", "pl-PL", "id-ID", "tr-TR", "ar-EG", "ru-RU", "fa-IR", "bg-BG", "hr-HR", "cs-CZ", "da-DK", "fi-FI", "lt-LT", "ms-MY", "nb-NO", "ro-RO", "el-GR", "he-IL", "hi-IN", "hu-HU", "sr-BA", "sk-SK", "sl-SI", "sv-SE", "tl-PH", "th-TH", "uk-UA", "vi-VN".
A note that you can use to add more details about the waiting room.
Only available for the Waiting Room Advanced subscription. Disables automatic renewal of session cookies. If true
, an accepted user will have session_duration minutes to browse the site. After that, they will have to go through the waiting room again. If false
, a user's session cookie will be automatically renewed on every request.
A list of enabled origin commands.
Only available for the Waiting Room Advanced subscription. If true
, requests to the waiting room with the header Accept: application/json
will receive a JSON response object with information on the user's status in the waiting room as opposed to the configured static HTML page. This JSON response object has one property cfWaitingRoom
which is an object containing the following fields:
Sets the number of new users that will be let into the route every minute. This value is used as baseline for the number of users that are let in per minute. So it is possible that there is a little more or little less traffic coming to the route based on the traffic patterns at that time around the world.
An ISO 8601 timestamp that marks when the next event will begin queueing.
An ISO 8601 timestamp that marks when the next event will start.
Sets the queueing method used by the waiting room. Changing this parameter from the default queueing method is only available for the Waiting Room Advanced subscription. Regardless of the queueing method, if queue_all
is enabled or an event is prequeueing, users in the waiting room will not be accepted to the origin. These users will always see a waiting room page that refreshes automatically. The valid queueing methods are:
HTTP status code returned to a user while in the queue. Available values: 200, 202, 429.
Lifetime of a cookie (in minutes) set by Cloudflare for users who get access to the route. If a user is not seen by Cloudflare again in that time period, they will be treated as a new user that visits the route.
Sets the total number of active user sessions on the route at a point in time. A route is a combination of host and path on which a waiting room is available. This value is used as a baseline for the total number of active user sessions on the route. It is possible to have a situation where there are more or less active users sessions on the route based on the traffic patterns at that time around the world.
Which action to take when a bot is detected using Turnstile. log
will have no impact on queueing behavior, simply keeping track of how many bots are detected in Waiting Room Analytics. infinite_queue
will send bots to a false queueing state, where they will never reach your origin. infinite_queue
requires Advanced Waiting Room. Available values: "log", "infinite_queue".
Which Turnstile widget type to use for detecting bot traffic. See the Turnstile documentation for the definitions of these widget types. Set to off
to disable the Turnstile integration entirely. Setting this to anything other than off
or invisible
requires Advanced Waiting Room. Available values: "off", "invisible", "visible_non_interactive", "visible_managed".