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...
Forum Discussion
I retested using the following.
when CLIENT_ACCEPTED {
TCP::collect 10
log "collecting"
}
when CLIENT_DATA {
log "Payload = [TCP::payload]
if {([TCP::payload 10] contains "HTTP") }{
log "Optimization"
pool Optimization_Pool
log "Optimization Pool"
}
else {
log "FW"
pool Firewall_Pool
}
TCP::release
}
I also noticed this in the release notes for 9.4. Could this be causing an issue also?
Using TCP::release and TCP::connect commands (CR63722)
If you use the TCP::release command in a CLIENT_DATA event, and then use the TCP::collect command to collect a specific amount of data, the TMM service becomes unavailable. To avoid this issue, use the TCP::collect command without an argument, and then use logic to determine whether enough data has been collected in the CLIENT_DATA event.