Score:0

Configure Keep Alive for connections coming from Cloudflare

bf flag
Tom

I have two servers, an NGINX load balancer that receives connections from Cloudflare and two Apache applications that receive requests forwarded by NGINX.

[Cloudflare] → [NGINX] → [Apache 01/Apache 02]

My Apache server will only be accessed through NGINX, and NGINX only accepts HTTP/HTTPs connections coming from Cloudflare.

By default NGINX always sends the user to the same Apache server he visited the first time (limitations due to background upload).

I already have Apache configured with Keep Alive. Should I also configure NGINX to keep connections alive?

ws flag
Yes, you need to explicitly enable keep alive to the upstream servers. For inward connections to nginx, this is enabled by default. Sticky sessions are a design time defect.
Tom avatar
bf flag
Tom
@symcbean So both in Apache and NGINX I have to enable Keep Alive. That?
ws flag
With a short network hop there's not huge gains to be made, but yes it needs to be enabled at both ends to work
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.