Forum Discussion
routing to a pool based on protocol
I have have a set of optimization servers that I want to route all http traffic to, and I want all other non-http traffic on port 80 to route to a different pool. This is what I have, but when non-htt...
hoolio
Cirrostratus
CirrostratusI'm fairly sure other people have used TCP::collect x in CLIENT_ACCEPTED and TCP::release in CLIENT_DATA, in 9.4.
I hadn't seen that CR before. Thanks for pointing it out. I checked AskF5 for more detail on it, but didn't find any solutions about it.
I think this issue doesn't apply to your rule, as you're using TCP::collect X in CLIENT_ACCEPTED and not using it in the CLIENT_DATA event.
Perhaps someone with access to CR notes could provide more detail on this?
If you change the collect to 10, do you get any logging in CLIENT_DATA? Else, what if you do try it collecting without a byte count?
Aaron
