F5 LTM (VE) - KeepAlive even if real server close connection

Hello Erlo,

 

 

 

As far as I understand your question, you could do the following:

 

- replace (using an iRule) the Connection: close header by something else in the HTTP_RESPONSE event.

 

 

Your client closes the connection because the server said it would not longer accept anything on this connection (e.g. your server sent the Connection: close header).

 

 

The problem lies with the fact that this header is passed on to the client, which then responds in kind by using a different connection. But the thing is: your client is connected to the F5 (which is a different TCP connection than the one the F5 has with your server) and can thus be kept open by telling the client it is not to be closed (through a Connection: keep-alive header for instance).

 

 

In the background, the F5 will need to issue a new connection to the server each time because the server will have closed the connection.

 

Using a OneConnect profile here will tell the F5 to 'establish and maintain some connections to the server' which can then be used to (even if one of those connections fail) still process the remaining http requests and replies.

 

 

 

Kind regards,

 

 

Thomas