Hi Fernando,
I haven't tested this so I'm not certain, but I believe that nothing will actually change in terms of serverside TCP connections if you only enable OneConnect Transformations on the HTTP profile, until you add a OneConnect profile. The online help in 10.0.1 lists the following:
Specifies, when checked (enabled), that the system performs HTTP header transformations for the purpose of keeping connections open. The default is enabled. This setting is applicable only when you configure a OneConnect pool.
This article notes the following when you use the HTTP profile option with OneConnect:
http://devcentral.f5.com/wiki/default.aspx/AdvDesignConfig/oneconnect.html
OneConnect with HTTP
Without OneConnect enabled, persistence data is examined only in the first request of a Keep-Alive connection, so if multiple requests are sent on the same clientside Keep-Alive connection, LTM will persist them all to the same destination as the first unless a OneConnect profile is applied (even if logic contained in an iRule dictates otherwise).
To allow HTTP/1.0 clients to re-use backend connections, apply a OneConnect profile and an http profile with OneConnect transformations enabled (enabled in default http profile).
With OneConnect transformations enabled, requests from HTTP/1.0 clients will be transformed into HTTP/1.1 requests using keepalives, allowing them to use OneConnect's HTTP/1.1 Keep-Alive connections as if they were v1.1 clients.
Clientside keepalives are not managed by OneConnect. LTM accepts keep-alive connections default and keepalive negotiation is managed by the client. The Max Requests option in the LTM http profile defaults to 0, allowing unlimited re-use of existing connections.
Aaron
Nimbostratus
