Chapter 5: Action Reference
An action takes arguments and is wrapped in a user-named action definition block. When the action definition is called from a policy rule, any actions it contains operate on their respective arguments. Within a rule, named action definitions are enabled and disabled using the action( )property.
Actions take the following general form:
action(argument1, ...)
An action block is limited to the common subset among the allowed layers of each of the actions it contains. Actions appear only within action definitions. They cannot appear in <Admin> layers.
Argument Syntax
The allowed syntax for action arguments depends on the action.
•String—A string argument must be quoted if it contains whitespace or other special characters. For example: log_message(“Access alert”).
•Enumeration—Actions such as delete( ) use as an argument a token specifying the transaction component on which to act. For example: a header name such as request_header.Referer.
•Regular expression—Several actions take regular expressions. For more information about writing regular expressions, refer to Appendix E, “Using Regular Expressions,” in the Blue Coat ProxySG Configuration and Management Guide.
•Variable substitution—The quoted strings in some action arguments can include variable substitution substrings. These include the various versions of the replacement argument of the redirect( ), rewrite( ), and rewrite( ) actions, and the string argument in the append( ), log_message( ), and set(header, string) actions. A variable substitution is a substring of the form:
$(name)
where name is one of the allowed substitution variables.
For a complete list of substitutions, see Appendix D: "CPL Substitutions".
Action Reference
The remainder of this chapter lists the actions and their accepted values. It also provides the context in which each action can be used and examples of how to use them.
