Forum Discussion
The-messenger
Cirrostratus
Sep 08, 2020TLSv1.3 validation not showing in SSL Labs
I'm running 14.1.2.7 on a VCMP guest, Host is running 14.1.2.1. I have removed the No TLSv1.3 option to enable 1.3 in my SSL Profile. When testing from SSL Labs, it returns No --- TLSv 1.3. I have e...
It is somewhat inconvenient. You could try something like setting a single local variable (not in RULE_INIT) in each rule to something unique and then build the variable names in that particular rule based on the first variable. Maybe an example would be easier to demonstrate:
rule rule1 {
when CLIENT_ACCEPTED {
set var_prefix "rule1"
set ${var_prefix}var1 "this is rule1's var1 value"
log local0. "$var_prefix variable name ${var_prefix}var1, variable value: [set [subst ${var_prefix}var1]]"
}
}
rule rule2 {
when CLIENT_ACCEPTED {
set var_prefix "rule2"
set ${var_prefix}var1 "this is rule2's var1 value"
log local0. "$var_prefix variable name ${var_prefix}var1, variable value: [set [subst ${var_prefix}var1]]"
}
}
Here is the sample output from a request to a vip with both rule1 and rule2 added:
Rule test_rule1 : rule1 variable name rule1var1, variable value: this is rule1's var1 value
Rule test_rule2 : rule2 variable name rule2var1, variable value: this is rule2's var1 value
I guess you could put in a feature request with F5 support asking for the scope of local variables to be limited to the rule they're set in, but I'm guessing there is a good reason for the way it is now.
Aaron