disable_all
enable_all
Description Stops execution of the current event after the event code section is finished by skipping the execution of following scripts for the current event. Does not affect the next execution of this type of event on this connection.
Full Syntax event disable_current
Description Disables the execution of specified event types for the rest of the connection (unless re-enabled).
Input Event names (space-separated).
Full Syntax event disable <event name>+
Description Re-enables the execution of specified event types.
Input Event names (space-separated).
Full Syntax event enable <event name>+
Description Disables the execution of all AppShape++ events for the rest of the connection (unless re-enabled).
Full Syntax event disable_all
Description Re-enables the execution of all AppShape++ events that were disabled previously on this connection.
Full Syntax event enable_all
filter
Description
Provides access to filter properties and allows Alteon to skip a filter.
Valid Events
CLIENT_ACCEPTED HTTP_REQUEST HTTP_REQUEST_DATA
Implementation Notes
All traffic events for informational sub-commands are applicable.
First Implemented Version
29.3.0
Description Returns the name of the currently matched filter, as defined in the configuration.
Returns an empty string if no name is configured, or no selection has been made.
Output The name of the current filter.
Full Syntax filter name
Description Returns the ID of the currently matched filter. Returns an empty string if no selection has been made.
Output The ID of the current filter.
Full Syntax filter id
Description Ignores the currently matched filter and continues to look for a filter matching the connection.
Full Syntax filter skip
Document ID: RDWR-ALOS-SDK-V3010_RG1502 49
group
Description
Accesses a server group, and lets you retrieve information about a group server.
Valid Events
First Implemented Version
29.0.0
Description Selects the specified group and, optionally, the specific real server belonging to the group, to which the command forwards the current session.
To be able to select a group for a virtual service, that group must be declared as active for that service, either via configuration or script declaration.
Input Group ID
Server ID or server IP (optional) Port (optional)
Full Syntax group select <group ID> [server <server ID | IP> [<port>]]
Alias pool <group ID> member <server ID>)
count
list
Description Retrieves the total number of configured servers (or only the number of configured servers that are active) in the specified group that are available for load balancing for the current service.
Output The number of servers (integer).
Full Syntax group count all_servers | active_servers <group ID>
Alias active_members <group ID> alias for group count active_servers <group ID>
members <group ID> alias for group count all_servers <group ID>
Description Retrieves all the servers configured (or only the configured servers that are active) for the specified group, in Tcl list format.
Output The list of servers.
Full Syntax group list all_servers | active_servers <group ID>
Document ID: RDWR-ALOS-SDK-V3010_RG1502 51
host
Description
Overrides the server selection mechanism and forwards the request to a specified host (IP and, optionally, port) that is not defined as a real server on Alteon.
Input
IP address Port (optional)
Full Syntax
host <IP> [<port>]
Valid Events
All
First Implemented Version
31.0.0
Implementation Notes
• If the port is not specified, traffic is sent to the initial destination port used by the client.
• The command is only valid for use in scripts attached to filters.
log
Description
Logs a specified message to the Alteon application services log. Also requires the following steps:
• AppShape++ logging is globally enabled on Alteon.
• The syslog is accessible through the data port, and not the management port.
• The /cfg/sys/mmgmt/syslog command is set to data.
• The /cfg/sys/syslog/sesslog command is enabled.
Input
The specified message.
The syslog facility (optional).
The severity level (optional).
Output
-s sends a message to the syslog server only.
-a sends a message to both the syslog and applog servers.
Full Syntax
log [-s |-a] [facility] [debug | info | warning | error] <message>
Valid Events
• The message can contain variables (that are replaced by a variable value), or command output (such as an IP address).
• By default the command logs the message only in the application services log.
Document ID: RDWR-ALOS-SDK-V3010_RG1502 53
First Implemented Version
29.0.0
md5
Description
Calculates the md5 value
Input
Text
Output
Hash value (32 bytes)
Full Syntax
md5 <text>
For example:
md5 [HTTP::uri]
Valid Events
All events
First Implemented Version
29.4.0
Document ID: RDWR-ALOS-SDK-V3010_RG1502 55
persist
Description
Enables implementing persistent connections and manipulating the persistency table.
Valid Events
This command can be used only when the selected group is known.
First Implemented Version
29.4.0
usid
cookie
Description Implements persistency by user-defined session ID.
Input session ID (string) timeout (optional)
Full Syntax persist usid <session id> [<timeout>]
Alias persist uie
Valid Events All client side events that run before LB_SELECTED.
Notes This command searches the persistency table for an entry that matches the provided session ID string, the current virtual service, and the selected group ID.
If found, traffic is forwarded to the server mentioned in the persistence entry.
If not found, an entry is created for future requests belonging to that session. The entry creation must take place after the server is selected.
Description Implements persistency for HTTP requests by specified cookie value, using either the cookie insert, cookie rewrite, or passive cookie mechanism.
Input cookie name
expires (optional) offset (optional) length (optional) timeout (optional)
Full Syntax persist cookie insert <cookie name> [expires <expires> [absolute
| relative] ] [path <path>] [domain <domain>] [secure <enable | disable>] [timeout <timeout>]
persist cookie rewrite <cookie name> [expires<expires> [absolute
| relative] ] [path <path>] [domain <domain>] [secure <enable | disable>] [timeout <timeout>]
persist cookie passive <cookie name> [{<offset> [<length>]}]
[timeout <timeout>]
Valid Events HTTP_REQUEST HTTP_REQUEST_DATA HTTP_CRULE_MATCH HTTP_CRULE_NOMATCH Notes
Expire and Timeout
The time that a persistency entry exists can be specified in terms of lifetime (entry is deleted X seconds after it was created), or timeout (entry is deleted Y seconds after the last time the persistency entry was looked up).
When the expires parameter is used or exists (in passive and rewrite server cookies), it defines an entry with lifetime. When a timeout value is used, it creates
Document ID: RDWR-ALOS-SDK-V3010_RG1502 57 Notes (cont.)
Cookie Insert
The cookie insert command searches for a specified cookie value in the HTTP request.
If found, the command retrieves the relevant server from the persistency table.
If not found, the command selects a server according to group metrics and on server response. A cookie with the specified name is inserted in the HTTP response, and a persistency table entry is added.
When no expires value is specified, or the value is 0, the expires parameter is not included in the Set-Cookie header. In such cases, Radware recommends that you specify a timeout value. The default timeout value is 10 minutes (600 seconds).
When the expires value is not 0, an expires parameter is included in the Set-Cookie header. In this case, the timeout option is not valid.