connection behavior with or without oneconnect
hi ,dear Irule according to test in lba,here is what I found for connection behavior with/without oneconnect all tests have http profile enabled,and source
1:without oneconnect profile after client----vs,vs---backend server connection established,after keep alive timeout is met,backend "fin ack" connection with F5,then VS "fin ack " with client.
2:with oneconnect profile after client----vs,vs---backend server connection established,after keep alive timeout is met,backend "fin ack" connection with F5,but VS doesn't send "fin ack " with client.
3:it seems client ,such as IE chrome doesn't hornor keep-alive:timeout in response from backend server even ,after the timeout value,it can still reuse the client side keep alive connection