Re: Clients occasionally see truncated responses

2021-04-09 Thread Nathan Konopinski
Thanks, Willy. I appreciate you taking the time to send a patch. Unfortunately, I'm still seeing the errors and multiple records being sent back to the clients When you say, I've just rechecked in the code and indeed, by default it will not limit. Does that mean tune.idletimer allows for the

Re: Clients occasionally see truncated responses

2021-04-09 Thread Willy Tarreau
Hi Nathan, On Thu, Apr 08, 2021 at 06:15:10PM -0700, Nathan Konopinski wrote: > One other behavior I've observed, nginx has an ssl_buffer_size ( > http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_buffer_size) > option that defaults to 16kb. As I decrease its value, I start seeing the >

Re: Clients occasionally see truncated responses

2021-04-08 Thread Nathan Konopinski
One other behavior I've observed, nginx has an ssl_buffer_size ( http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_buffer_size) option that defaults to 16kb. As I decrease its value, I start seeing the same body size != content length errors from clients. I tried experimenting with

Re: Clients occasionally see truncated responses

2021-04-02 Thread Willy Tarreau
On Thu, Apr 01, 2021 at 06:48:59PM -0700, Nathan Konopinski wrote: > Sorry about that. Here's a capture of the problem. Clients report errors > when they get two TLS app data packet responses. Nginx always sends a > single and haproxy usually but not always sends a single. The content > length of

Re: Clients occasionally see truncated responses

2021-03-31 Thread Willy Tarreau
On Wed, Mar 31, 2021 at 09:55:15AM -0700, Nathan Konopinski wrote: > Thanks Willy, that is what I'm seeing, capture attached. Clients only send > GETs, no POSTs. What are possible workarounds? Is there a way to ignore the > client close and keep the connection open longer? It's not what happens

Re: Clients occasionally see truncated responses

2021-03-31 Thread Willy Tarreau
Hi Nathan, On Tue, Mar 30, 2021 at 09:21:30AM -0700, Nathan Konopinski wrote: > Sometimes clients (clients are only http 1.1 and use connection: close) are > reporting a body length of ~4000 is less than the content length of ~14000. > The issue does not appear when using nginx as an LB and I've

Clients occasionally see truncated responses

2021-03-30 Thread Nathan Konopinski
Sometimes clients (clients are only http 1.1 and use connection: close) are reporting a body length of ~4000 is less than the content length of ~14000. The issue does not appear when using nginx as an LB and I've verified complete responses are being sent from the backends for the requests clients