Change server SSL profile based on HTTP content

Essentially the oneconnect profile is used IN ADDITION to what you have already configured in your irule/LTM profile. Without a oneconnect profile, your only option is to create a brand new serverside connection every time your header changes. With a oneconnect profile, you can have persistent serverside connections to your two destinations "kept open" and then, depending on the header in the client request, it will just send it to an available connection instead of creating a new one.

That said, oneconnect is not going to pipeline multiple clients to a single server connection, it'll only use an existing connection if that connection is IDLE. If there are no IDLE serverside connections, it'll create a new one, similarly, if you don't meet the mask (for example a /32 mask means clients can only reuse their own connections, whereas a /24 you could let clients with source ips in the same subnet share connections with each other) criteria, it'll also create a new connection (even if there is an idle one for a different mask). The interaction of all this various logic probably explains what you observed as "inconsistent".

It is definitely one of the stranger profiles to understand and tune, but it sounds to me like if you keep your current setup and just add a /32 oneconnect, and it has a timeout that is, say, about twice as long as what you would estimate as the average time between user requests with headers for DIFFERENT destinations, you'd probably see some performance gain.

On the other hand, you can just create new connections every time like you are now, if you have the memory to spare. As long as your tcp idle timeout is reasonable and connections get culled regularly, the impact on the box isn't serious (although your users will obviously experience the delay of a tcp + tls handshake every time the headers switch)

Thanks again for the update :-)

Regarding the mask - I had left it at default because the VS uses a SNAT pool with a single IP. My understanding is that oneconnect examines the post SNAT source IP, so essentially the mask has no impact for my setup? I did try with /32 just to check but saw no difference.

As for my question on what 'level' the oneconnect reuse pool operates at - looking at the help section in the oneconnect profile page on the F5 GUI it looks like it is at the VS level. I think that will likely cause me a problem for the current setup (not tied to that setup though, happy to change it :-). I use different pools so that an iRule can assign a server SSL profile based on a 1-1 mapping between the pool name and the SSL profile to use.

To me the following is what I _suspect_ is happening:

- Initial traffic sent to pool A and server side connection setup correctly using server SSL profile A

- When HTTP header change happens, the traffic policy instead chooses pool B

- Oneconnect kicks in at this point and sees that the required connection is from SNAT IP to website IP port 443. This is on pool B but that was chosen by the VS with the oneconnect profile, and the mask covers the source IP OK, so this connection is eligible to be switched onto a reused TCP connection.

- At the TCP level i.e. IP/port this new connection request in pool B exactly matches the existing connection from pool A. Also at this point the server SSL profile would match, because I can't assign that in the iRule until a serverside event (please correct me if I have that wrong). This is why I asked if oneconnect takes the likes of SSL into account to differentiate between connections or if it is just on the lower level protocol.

- Oneconnect switches the traffic onto the existing connection, and the SERVER_CONNECTED event never triggers, which is where I would have assigned server SSL profile B

So basically all my traffic is just going over that single connection, and any time that HTTP Header X = B the traffic is actually sent on the 'wrong' pipe.

I can see how oneconnect would work if I could somehow confine it to a pool rather than a VS. Essentially I would then just use it to keep a connection up per pool, and I would know that each connection had been established using the correct SSL profile, so any traffic directed to the pool by the traffic policy would definitely be sent across a 'correct' pipe. Is this possible?

Sorry, there is a lot to clarify and explain and possibly correct in that and I think we are getting beyond the scope of DevCentral. As I mentioned before, the name, usage, and configuration of a oneconnect profile is confusing and a little unintuitive. If you are expecting to see "one" connection per pool, you will definitely think it is behaving incorrectly, because it is not a "tunnel" or a "pipe" like you are saying. It is a tcp connection and it will never be used for multiple requests at the same time, it must be idle or a new connection will be created. In fact, some people put the default oneconnect profile on vips hoping for a "one click" performance improvement only to find they now have more serverside connections than before (especially if their non-oneconnect vip was layer 4 or was doing pipelining etc).

Ultimately, there is only so much that can be done here. If you are able to get something that works for you taking this conversation (and others here) into consideration, great. If not, you should probably work with someone with whom you can share specific config details and pcaps and get personalized consulting that should not be done over public internet.

Thanks again for the reply.

Apologies for the confusion in the terms that I used. Please note that I do not expect multiple clientside TCP connections to be multiplexed onto a single serverside TCP connection. I was saying one serverside connection per pool because I was focusing on the simple example being discussed – a single clientside TCP connection which in my case should result in 2 completely separate TCP connections serverside – one per pool (one ACTIVE, one IDLE, assuming IDLE hadn’t timed out yet). This same connection layout would then scale up as new concurrent clientside connections were activated. 

In fact in my case the traffic profile is sort of round the other way to how oneconnect is normally used. Depending on traffic volume/profile I would generally expect to see more serverside connections than clientsdie in my specific case, whereas the normal deployment would generally result in fewer serverside connections compared to clientsdie.

I used the term “pipe” because the simple term TCP connection seems a little to vague to me. All the oneconnect documentation I have read simply mentions TCP connections, but as I see it these connections are much more than that. They are fully established connections using higher level protocols ready to take Layer 7 HTTP request/response messages. In my case the important piece of info that the term “TCP connection” leaves out is regarding SSL. So I should maybe use (TCP+SSL-A) and (TCP+SSL-B). At the TCP level these two connections will look exactly the same, but if you take the higher level protocol stack into consideration they are actually very different connections (what I meant by “pipe” – I realise though that I said it with no explanation/context so it will have been very confusing, apologies).

It feels to me like oneconnect is working solely at the TCP level and ignoring the higher level components. This would work fine for a normal setup where the Virtual Server had just one server SSL profile – however in my case I use different server SSL profiles which it feels like oneconnect may simply ignore.

However I realise I probably have this wrong, as a more normal scenario would be the F5 acting as reverse proxy in front of a number of internal webservers which host multiple domains and use SNI to confirm which connection aligns with which FQDN. I assume oneconnect must have a way to cope with this situation and if I understood that operation then elements of it would likely be relevant in my case.

Anyway I see that this is getting too complicated to bottom out in the format of this forum. Thank you for taking the time to try to help though, it is greatly appreciated 😊