Forum Discussion
NimbostratusBigIp and Keep-Alive feature
Hi all, I have a question about the BigIp load-balancer configuration. The configuration is based on a BigIp linked to a unique server. The HTTP Keep-Alive feature of the server is activated. Unfortunately the team in charge of this server can't deactivate this one. For our Siteminder infrastructure, it's mandatory to deactivate the HTTP Keep-Alive feature for all applications. So my question is: Is it possible with a specific configuration of the BigIp load-balancer to "break" the HTTP Keep-Alive feature to be conform with our recommandations? FYI, the "OneConnect" profile of the BigIp is already set to "None" but it isn't enough for switching off the feature. Have a nice day. Michel
3 Replies
What_Lies_Bene1Cirrostratus
Hmmm, not sure this is possible in any simple way. You should be able to disable the HTTP Pipelining & Persistent Connections features in the HTTP profile assigned to the VS but I suspect this will only apply client-side. That being said, if Keep Alives are not seen/allowed client side perhaps the logic is setup so that such features are not used server side. I'd try it and then test.
If it doesn't work we'd be looking at an iRule to remove the Keep Alive header from server side requests as they leave the device.
mbadet_119292Thanks a lot for this answer. Have a nice day. Michel
- What_Lies_Bene1You're welcome. It would be great if you could let us know how this works out.
