Keep alive settings

[marklcfc]

Regarding these few posts did we ever find out why and is it fixed or not? My host is still limiting my keep alive to 10 @ptprog @Matt @Charles

 

[ASTRAPI]

I am using keep alive on a well optimized environment with the value of 5 and i do not recommend higher values.

But that's me ?

[bearback]

Quote

The KeepAlive issue can be "solved" editing the file "system/Output/Output.php", and removing the line "$this->sendHeader( "Connection: close" );".

The question was never answered by IPB staff and I am interested as to why IPS has disable the Keep Alive? what are the benefits by disabling keep alive? there must be a reason for it being disabled?

Would there be any performance increase having it re-enabled? or any negative effects?

Thanks

[ptprog]

Note that with HTTP2 that header is less important (actually, I think with HTTP2 the header is dropped).

Since I moved to SSL and enabled HTTP2, I stop caring about that.  While I was manually enabling the Keep-alive, I never noted issues with IPS.

About the effects, it should reduce latency in certain situations, but it will increase memory used by the web server (depending on the server configuration, this may or may not be significant).

[bearback]

On ‎5‎/‎31‎/‎2018 at 8:56 PM, ptprog said:

Note that with HTTP2 that header is less important (actually, I think with HTTP2 the header is dropped).

Since I moved to SSL and enabled HTTP2, I stop caring about that.  While I was manually enabling the Keep-alive, I never noted issues with IPS.

About the effects, it should reduce latency in certain situations, but it will increase memory used by the web server (depending on the server configuration, this may or may not be significant).

thank you for your reply

[bfarber]

The connection is closed so as to allow background tasks to run after the the page has "finished" loading in some configurations, but really you're better off putting your efforts into using http/2 rather than focusing on this these days.