Forum Discussion
LB::reselect node stops cookie injection??
I have a iRule to send sever side traffic to a uniqute port based on the virtual's destination port. I know this can be done with different pools, but in this case, we have a pool members that do not specify a port.
when HTTP_REQUEST {
set flag 0
}
when LB_SELECTED {
if {([TCP::local_port] == 80) and ($flag == 0) } {
set flag 1
set RESELECT [lindex [LB::select] 3 ]
LB::reselect node $RESELECT 8009
}
elseif {([TCP::local_port] == 443) and ($flag == 0) } {
set flag 1
set RESELECT [lindex [LB::select] 3 ]
LB::reselect node $RESELECT 8010
}
}
The rule works great. I've used it before. Traffic is going to the servers on the proper backend port.
But I noticed that the LTM stopped injuecting the persistance cookie in my persistance profile. I am not seeing the cookie in the HTTP response header at all. Remove the iRule and the cookie is injected. Any thoughts??
10.2.4 Build 655.0 Hotfix HF4
1 Reply
- nitass
Employee
But I noticed that the LTM stopped injuecting the persistance cookie in my persistance profile. I am not seeing the cookie in the HTTP response header at all. Remove the iRule and the cookie is injected. Any thoughts??i understand because you are using node (not pool).
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com