For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

fbarbero_29110's avatar
fbarbero_29110
Icon for Nimbostratus rankNimbostratus
Sep 22, 2009

OneConnect Transformations

Hi everyone,

 

 

Looking at old topics in this forum there were some posts regarding this issue back in 2007 and I wonder if something has changed since about the above topic.

 

 

We have a client which is using OneConnect transformations on an http type profile but has no OneConnect profile applied to any virtual server.

 

 

What would be the expected behaviour?, do we gain any extra capacity or improvement on performance on server side?

 

 

Thanks in advancem,

 

 

Regards

 

 

Fernando
config
design

2 Replies

  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Sep 22, 2009
    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
  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Jun 20, 2011
    I tested this for a customer and confirmed that the Connection header on the serverside is only modified if both OneConnect Transformations is enabled on the HTTP profile and a OneConnect profile is added to the virtual server.

     

     

     

    OneConnect | OneConnect | HTTP | Resulting Connection

     

    transformation | profile | version | header value on serverside

     

    ------------------------------------------------------------------------------------

     

    Disabled | Disabled | 1.0 | Connection: Close

     

    Disabled | Disabled | 1.1 | Connection: Close

     

    Enabled | Disabled | 1.0 | Connection: Close

     

    Enabled | Disabled | 1.1 | Connection: Close

     

    Disabled | Enabled | 1.0 | Connection: Close

     

    Disabled | Enabled | 1.1 | Connection: Close

     

    Enabled | Enabled | 1.0 | Connection: Keep-Alive

     

    Enabled | Enabled | 1.1 | X-Cnection: Close

     

     

     

    Aaron