Support for Sticky Sessions with WebSocket Connections #1555

Closed
opened 2026-04-05 19:34:18 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @clemone210 on 4/30/2025

Hello,

When using multiple targets for a resource, load balancing is automatically enabled.

However, it appears that WebSocket (wss://) connections are currently also load balanced independently of the initial HTTPS session. This leads to situations where the initial session is established on one target but the WebSocket connection is redirected to another, resulting in session mismatch or connection failure.

Is there currently a way to configure sticky sessions so that WebSocket connections are routed to the same target as the initial session? If not, it would be great to see support for sticky load balancing added in a future release.

Let me know if I'm missing a configuration option, or if this behaviour is expected for now.

Thanks for your work on this project!

*Originally created by @clemone210 on 4/30/2025* Hello, When using multiple targets for a resource, load balancing is automatically enabled. However, it appears that WebSocket (`wss://`) connections are currently also load balanced independently of the initial HTTPS session. This leads to situations where the initial session is established on one target but the WebSocket connection is redirected to another, resulting in session mismatch or connection failure. Is there currently a way to configure sticky sessions so that WebSocket connections are routed to the same target as the initial session? If not, it would be great to see support for sticky load balancing added in a future release. Let me know if I'm missing a configuration option, or if this behaviour is expected for now. Thanks for your work on this project!
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1555