What is HTTP Part VII - OneConnect

In the last article in this What is HTTP? series we finished covering the settings in the HTTP profile itself. This week, we begin the transition to technologies that support, enhance, optimize, secu...
Published Nov 06, 2017
Version 1.0
application delivery
http
LTM
oneconnect
series-what-is-http
TMOS
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
dragonflymr's avatar
dragonflymr
Icon for Cirrostratus rankCirrostratus
Jan 15, 2018

Hi,

 

Thanks for answers.

 

Considering point 4. Sure it's counter, but after counter counts to set value it could marke connection as illegible for reuse - same as for Max Age, then use identical algorithm - if next client request is first then it is closed by BIG-IP if server keep alive is first then server closes connection.

 

I am a bit unsure about your logic here, for both settings server is not aware what is going on on BIG-IP side so why to use separate algorithms for Max Age and Max Reuse?

 

Piotr