Solved
Forum Discussion
Michele_Cereda_
Nimbostratus
The problem seemed to be caused by the Type parameter of the VS, that was set on Performance (Layer 4) instead of Standard.
Now the code is working. Thanks for your advices.
The thing that seems strange to me about this particular topic is that the editor warned me that the VS needed a different profile in case I tried to set something like that. Do you have any ideas why it didn't this time?
IanB
Mar 19, 2016Employee
Sorry about the delay. I can confirm that this is expected behaviour when using FastL4 + HTTP. The HTTP profile was enhanced to allow it be added to a fastL4 to support the PEM product, but it is currently quite limited in what it can do (see SOL16446), as the intended use was only with the PEM. module.
As a result, in this scenario, HTTP_REQUEST fires after LB_SELECTED, at which point it is too late to change the selected pool member. As you've noted, modifying the virtual server to be of type 'standard' resolves the issue.