Let’s discuss various HAProxy Websocket Timeouts in this article. Bobcares, as a part of our Server Management Service offers solutions to every query that comes our way.

HAProxy Websocket Timeouts

When referring to HAProxy with WebSocket apps, the timeout refers to the setup options within HAProxy. This specifies how long WebSocket connections can go without any use before closing it. These timeouts are essential for controlling WebSocket connection lifecycles and guaranteeing resource usage.

The various timeouts that HAProxy allows us to set for WebSocket connections are as follows:

Client Timeout

The client timeout, also known as the “client-idle timeout” or “timeout client,” establishes the maximum amount of time that the client (such as a WebSocket client or browser) and the HAProxy server may go without communicating. The WebSocket connection will end if the client doesn’t send any data within this time.

In order to release resources when clients become inactive and make server resources available for other connections, it is crucial to configure a suitable client timeout.

Server Timeout

The server timeout, also known as the “server-idle timeout” or “timeout server,” determines the maximum time that HAProxy and the backend WebSocket server may go without activity. The WebSocket connection to the backend server will end if there is no data transfer during this time between HAProxy and the server.

The server timeout must be proper in order to free up resources on the backend server side when WebSocket connections are not in use.

Timeout Tunnel

WebSocket connections are directly associated with the “timeout tunnel” configuration. It specifies the longest time a WebSocket tunnel can be active without any data transfer taking place between the client and the server. Once the WebSocket connection has been made, this timeout is in effect.

In order to avoid resource exhaustion from WebSocket connections remaining open indefinitely, it’s crucial to set the proper timeout tunnel value.

Timeout Connect

The amount of time HAProxy can take to connect to a backend WebSocket server is specified by the “timeout connect” parameter. Since HAProxy offers high availability, it may deem the server to be unavailable and go on to try another server if it is not possible to make a connection within this time limit.

It’s crucial to set a sufficient timeout connect value to prevent long waits when connecting to backend servers.

[Searching solution for a different question? We’re happy to help.]

Conclusion

The effectiveness of configuring these HAProxy WebSocket timeouts depends on the requirements of the individual apps and the state of the network.