Lists the two cookie commands and shows how to use them.

Demonstrates the sub-function to handle the cookie attribute "SameSite" and others.

Used to perform cookie encryption/decryption on behalf of the real server.

The sample Waiting Room script demonstrates how you can place visitors in a virtual queue instead of denying them service directly when the server side reaches its configured capacity limit during high-demand situations. In this virtual Waiting Room, visitors can see their position in line and when their turn arrives, they are redirected to the requested page.

Configuration parameters include the waiting room name, total resource limit threshold (default is 1000), and the Resource URL applicable to the waiting room. You can also customize the message displayed to users when they are placed in the waiting room by editing the HTML page section of the script.

Required data structures such as atomic counters and shared tables are already built into the script; however, you have the option to apply user-defined atomic counters and shared tables to customize the script.

Redirects requests to a URL with user-defined code and cookie.

Note: Do not use this script "as is". Instead, copy and customize the code, URL, and cookie.

Redirects requests to the HTTPS site.

Note: This script can be used directly without making any changes.

Redirects requests to the specified HTTPS URL.

Note: This script can be used directly without making any changes.

Collects data in HTTP request body or HTTP response body. In HTTP_REQUEST or HTTP_RESPONSE, you could collect specified size data with “size” in collect().In HTTP_DATA_REQUEST or HTTP_DATA_RESPONSE. You could print the data use “content”, calculate data length with “size”, and rewrite the data with “set”.

Note: Do not use this script "as is". Instead, copy it and manipulate the collected data.

Finds a specified string, removes a specified string, or replaces a specified string to new content in HTTP data.

Note: Do not use this script "as is". Instead, copy it and manipulate the collected data.

Inserts a 32-bit hex string into the HTTP header with a parameter “Message-ID”.

Note: This script can be used directly without making any changes.

Redirects requests based on the status code of server HTTP response (for example, a redirect to the mobile version of a site).

Note: Do not use this script "as is". Instead, copy it and customize the condition in the server HTTP response status code and the URL values.

Redirects requests based on User Agent (for example, a redirect to the mobile version of a site).

Note: You should not use this script "as is". Instead, copy it and customize the User Agent and URL values.

Rewrites the host and path in the HTTP request, for example, if the site is reorganized. You should not use this script as is. Instead, copy it and customize the "old" and "new" hostnames and paths.

Rewrites HTTP location to HTTPS, for example, rewrite “Location:http://www.example.com” to “Location:https://www.example.com”.

Note: This script can be used directly without making any changes.

Rewrites HTTP referer to HTTPS, for example, rewrite “Referer: http://www.example.com” to “Referer: https://www.example.com”.

Note: This script can be used directly without making any changes.

Rewrites HTTPS location to HTTP, for example, rewrite “Location:https://www.example.com” to “Location:http://www.example.com”.

Note: This script can be used directly without making any changes.

Rewrites HTTPS referer to HTTP, for example, rewrite “Referer: https://www.example.com” to “Referer: http://www.example.com”.

Note: This script can be used directly without making any changes.

Shows how to use those "magic characters" which have special meanings when used in a certain pattern. The magic characters are ( ) . % + - * ? [ ] ^ $

Stores a request header value in an event and uses it in other events. For example, you can store a URL in a request event, and use it in a response event.

Note: Do not use this script "as is". Instead, copy it and customize the content you want to store, use collect() in HTTP_REQUEST to trigger HTTP_DATA_REQUEST,or use collect() in HTTP_ RESPONSE to trigger HTTP_DATA_ RESPONSE.

Used to get various types IP Address and port number between client and server side.

Uses demo_1 and demo_2 script to show how multiple scripts work. Demo_1 with priority 12 has a higher priority.

Note: You could enable or disable other events. Do NOT use this script "as is". Instead, copy it and customize the operation.

Uses demo_1 and demo_2 script to show how multiple scripts work. Demo_2 with priority 24 has a lower priority.

Note: You can enable or disable other events. Do not use this script "as is". Instead, copy it and customize the operation.

Lists the RAM caching event and commands.

Demonstrates how to use script to do dynamic RAM caching.

Note: Dynamic caching is identified by a configured ID. Ensure the RAM caching configuration is selected in the HTTP or HTTPS profile.

Demonstrates how to create multiple variations based on client IP address. The sort of grouping applies to both regular caching and dynamic caching.

Note: Ensure the RAM caching configuration is selected in HTTP or HTTPS profile.

Routes to a pool member based on URI string matches.

Note: You should not use this script as is. Instead, copy it and customize the URI string matches and pool member names.

Routes to a pool member based on IP address in the X-Forwarded-For header.

Note: You should not use this script as is. Instead, copy it and customize the X-Fowarded-For header values and pool member names.

Demonstrates how to use persistence commands and event.

The PERSISTENCE event is triggered when FortiADC receives the HTTP REQ and is ready to dispatch to the real server.

You can set the entry in PERSISTENCE, then look up it in POST_PERSIST.

FortiADC will dispatch to the dedicated server according to your entry set in PERSISTENCE if this session has not been assigned to the real server before.

Performs optional client authentication.

Note: Before using this script, you must have the following four parameters configured in the client-ssl-profile:

• client-certificate-verify—Set to the verify you'd like to use to verify the client certificate.
• client-certificate-verify-option—Set to optional
• ssl-session-cache-flag—Disable.
• use-tls-tickets—Disable.

Demonstrates how to fetch the SSL certificate information and some of the SSL connection parameters between server and client side.

Allows you to overwrite client source address to a specific IP for certain clients, also support IPv4toIPv6 or IPv6toIPv4 type.

Note: Make sure the flag SOURCE ADDRESS is selected in the HTTP or HTTPS type of profile.

Allows user to customize the TCP_send buffer and TCP_receive buffer size.

Demonstrates how to the TCP:sockopt with usage examples.

Demonstrates how to reject a TCP connection from a client in TCP_ACCEPTED event.

Demonstrates how to use AES to encryption/decryption data and some tools to generate the digest.

Allows you to create and configure shared atomic counters that are accessible by multiple httproxy processes within one VS. The stored data is located in shared memories.

In the Waiting Room setup, the atomic counters track variables at running time, including the current resource count, the current position in line, and the current total number of users in the waiting queue.

Demonstrates how to use the class_match and class_search utility function.

Compares an IP address to an address group to determine if the IP address is included in the specified IP group. For example ,192.168.1.2 is included in 192.168.1.0/24.

Note: Do not use this script "as is". Instead, copy it and customize the IP address and the IP address group.

Used to fetch the GEO information country and possible province name of an IP address.

Allows you to create and configure shared hash tables that are accessible by multiple httproxy processes within one VS. Both the table and stored data are located in shared memories.

In the Waiting Room setup, the shared table is used to track current active resource occupiers such as active sessions.

Demonstrates how to use those URL tools to encode/decode/parser/compare.

Demonstrates how to use the basic string operations and random number/alphabet, time, MD5, SHA1, SHA2, BASE64, BASE32, table to string conversion, network to host conversion utility function