Re: WebSocket + compression + timeout tunnel broken in v1.7?

On Tue, Mar 21, 2017 at 03:07:37PM +0200, Kristjan Koppel wrote: (...) > I can also confirm that this change fixes the problem for me in v1.7.3. Thanks for confirming, it's always encouraging! Willy

Re: WebSocket + compression + timeout tunnel broken in v1.7?

Hi! On Tue, 21 Mar 2017 08:46:57 +0200 Willy Tarreau wrote On Mon, Mar 20, 2017 at 10:28:41AM +0100, Christopher Faulet wrote: > Thanks for this detailed report. You're right. This is a bug and it was > fixed in 1.8. It will soon be backported in 1.7. If you're cur

Re: WebSocket + compression + timeout tunnel broken in v1.7?

On Mon, Mar 20, 2017 at 10:28:41AM +0100, Christopher Faulet wrote: > Thanks for this detailed report. You're right. This is a bug and it was > fixed in 1.8. It will soon be backported in 1.7. If you're curious, the > commit fixing the bug is e600624 ("BUG/MEDIUM: filters: Fix channels > synchroniz

Re: WebSocket + compression + timeout tunnel broken in v1.7?

Le 17/03/2017 à 11:57, Kristjan Koppel a écrit : Hi! I upgraded a HAProxy instance from v1.6.10 to v1.7.3 with no changes to configuration and I noticed that now clients connecting to a WebSocket backend are getting disconnected after being idle for "timeout client" time rather than the much lon

RE: WebSocket + compression + timeout tunnel broken in v1.7?

rom Coscend Communications Solutions' posted at: http://www.Coscend.com/Terms_and_Conditions.html From: Kristjan Koppel [mailto:krist...@ppesa.org] Sent: Friday, March 17, 2017 5:57 AM To: haproxy Subject: WebSocket + compression + timeout tunnel broken in v1.7? Hi! I upgraded a HAPro

WebSocket + compression + timeout tunnel broken in v1.7?

Hi! I upgraded a HAProxy instance from v1.6.10 to v1.7.3 with no changes to configuration and I noticed that now clients connecting to a WebSocket backend are getting disconnected after being idle for "timeout client" time rather than the much longer "timeout tunnel" time. As I understand it,