Forum Discussion
force BIG-IP to immediately reflect config changes
Yes, that's to be expected. I guess as an alternative you could greatly reduce the TCP connection timeout client-side in the hope that connections are closed (and therefore re-established) more often or worse yet, drop everything down to HTTP/1.0 and/or disable HTTP pipelining. Either way, you are massively increasing your protocol overhead and this isn't desirable.
It would be much better to instruct users to close and restart their browsers or alternatively, only make changes out of hours. Are these options for you?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com