Forum Discussion

Deb_Allen_18's avatar
Deb_Allen_18
Historic F5 Account
May 31, 2006

ONECONNECT:: command usage question

Hi all --

 

 

Can the ONECONNECT::* commands be used to replicate the existing OneConnect product feature for non-HTTP traffic?

 

How would such a rule be constructed?

 

 

I have a customer who wants to create something resembling OneConnect for a proprietary non-HTTP request/response protocol, so they can re-use an existing backend connection for new requests, rather than opening a new socket.

 

 

I ran across a couple of ONECONNECT:: commands, but usage is not well documented in the wiki, and the only examples I can find in this forum are specific to ending a OneConnect backend connection to re-establish with a different server when conditions change.

 

 

thanks!

 

/deb
application delivery
dev
devops
iRules

3 Replies

  • Colin_Walker_12's avatar
    Colin_Walker_12
    Historic F5 Account
    May 31, 2006
    If you check the Wiki to see the Events under which the ONECONNECT:: commands are available, you'll see that they are only currently available under some of the HTTP events. This means you likely won't be able to use them with other protocols at this time.

     

     

     

    Colin
  • Deb_Allen_18's avatar
    Deb_Allen_18
    Historic F5 Account
    Jun 19, 2006
    Well, I was after more info re: the undocumented ONECONNECT::detach, and ONECONNECT::reuse commands referenced in the the link I originally posted...

     

     

    ...but I'm reading between the lines here that all we need to do is apply a OneConnect profile to the non-HTTP virtual server to emulate OneConnect behaviour for non-HTTP protocols?

     

     

    So if we have no requirement to change servers midstream during a client connection, but only want to re-use the backend connection once it goes idle, then no iRule is even required?

     

     

    thanks for clarifying

     

    /deb