Persistent HTTP connections

At the HTTP communication layer, WebSEAL maintains persistent connections between the client browser and WebSEAL, and between junctioned web servers and WebSEAL.

Client connections are controlled by the following entries in the [server] stanza of the WebSEAL configuration file:

max-idle-persistent-connections

Maximum number of idle client persistent connections.

persistent-con-timeout

Maximum number of seconds that WebSEAL holds an HTTP persistent connection open for a new request before the connection is shut down.

disable-timeout-reduction

Whether WebSEAL reduces the timeout duration to help control the number of active worker threads. By default, WebSEAL automatically reduces the timeout duration for threads as the number of in-use worker threads increases.

Junction connections are controlled by the following entries in the [junction] stanza of the WebSEAL configuration file:

max-cached-persistent-connections

Maximum number of persistent connections stored in the cache for future use.

persistent-con-timeout

Maximum number of seconds a persistent connection can remain idle in the cache before WebSEAL closes the connection.

WebSEAL supports HTTP/1.1 persistent connections. HTTP/1.0 persistent connections are not supported.

Parent topic: Communication protocol configuration