Forum Discussion
NimbostratusHTTP_CLASS_SELECTED unavailable in 11.4.0 - any alternatives?
Hi all,
I've started investigating the requirements of upgrading from v10.2.4 HF4 to v11.4.0 HF1 and come across a problem.
We disable ASM for certain requests to one of our virtuals and currently achieve this by setting a variable for the desired traffic, then checking for that variable at the HTTP_CLASS_SELECTED event:
when HTTP_REQUEST {
set disable_asm 0
if {some logic here ==0} {
set disable_asm 1
}
}
when HTTP_CLASS_SELECTED {
if {$disable_asm==1}{
ASM::disable
}
}
This works great on v10.2.4 but HTTP_CLASS_SELECTED is being removed from v11.4.0 so I'm unsure what to do. SOL14381 makes some suggestions around using POLICY::names, however POLICY:: doesn't appear to exist on my current version.
Is it a case of removing this logic for the upgrade then once on v11' adding the recommendations from SOL14381? What I'd really like is something that will work now *and* transfer nicely when I perform the upgrade.
Can anyone suggest a way to disable ASM based on a variable value, that will work on v10.2.4 and v11.4.0?
Cheers, Steve.
2 Replies
TortiCirrus
Hi,
a little bit late, but...
As you have already seen, HTTP classes are removed @ 11.4.
So, the function HTTP_CLASS_SELECTED was removed, too. If you want to remove the ASM, you have to do this at HTTP_REQUEST (described in the SOL14381).
I still didn't try POLICY::names, because it isn't supported by irule ditor.
But where is the problem? Instead of "set disable_ASM 1", you have to write "ASM::disable".
regards- Kevin_Stewart
Employee
You can actually achieve this directly in the GUI now with Centralized Policy Management (CPM) in 11.4. It's under Local Traffic - Policies.
1. Create a policy that requires http and controls asm.
2. Create a rule that looks for your request condition (ex. http-uri starts-with /foo).
3. Set the action to disable asm.
You should be good to go.
