You should very be care for using HTTP profile with OneConnect profile together when you apply this feature on http traffic. It is a requirement, but not a recommendation or suggestion. Without HTTP profile, you will not be able to perform oneconnect translations and the TMM may reply server response to incorrect client if the original client close connection by sending FIN.
I'm not sure I understand your point here, but to clarify, OneConnect requires TCP and to functional properly, a layer 7 transactional protocol like HTTP. But HTTP profile does not require a OneConnect profile, that decision depends on the type of traffic.
Please guide Source NAT , Destination NAT and Auto NAT Why it is required and how it works
Thanks Jason for this article I was wondering when this session will come as I posted in community also .. Nicely explained
What if server closes the connection?.....will one connect still maintain the connection as idle in f5?
Json, we are using one-connect with a snat pool of 3 IPs. How many requests each IP can handle per second? Sorry if my question is confusing.
Great explanation
You should very be care for using HTTP profile with OneConnect profile together when you apply this feature on http traffic. It is a requirement, but not a recommendation or suggestion. Without HTTP profile, you will not be able to perform oneconnect translations and the TMM may reply server response to incorrect client if the original client close connection by sending FIN.
I'm not sure I understand your point here, but to clarify, OneConnect requires TCP and to functional properly, a layer 7 transactional protocol like HTTP. But HTTP profile does not require a OneConnect profile, that decision depends on the type of traffic.