From: "Michael Ströder" <michael@stroeder.com>
To: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: Websocket close 1006 (abnormal closure): unexpected EOF
Date: Fri, 8 Jan 2021 15:24:51 +0100 [thread overview]
Message-ID: <e189df9b-0599-9f62-c7a6-fd634b0e27db@stroeder.com> (raw)
In-Reply-To: <87wnwn7eid.wl-jch@irif.fr>
On 1/8/21 2:19 PM, Juliusz Chroboczek wrote:
>>> I just normally put
>>> proxy_read_timeout 1200s;
>>> proxy_send_timeout 1200s;
>
>> 20min? Really? Even 120s would be quite long.
>
> I've reduced the keepalive timeout to be 45 to 55s (depending on how the
> timer gets scheduled), even though I rather agree with Toke.
Yeah, I've installed that right now.
> Scratch
> that, Toke is not radical enoough: the default timeout for WebSockets
> should be 2 hours 4 minutes, for consistency with RFC 5382 REQ-5.
Noted.
> The tradition to use small timeouts comes from Apache, which used to use
> up a whole process for every connection, even when idle.
This should not be an issue with Apache's MPM event model anymore. Right?
Ciao, Michael.
next prev parent reply other threads:[~2021-01-08 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 10:56 [Galene] " Jeroen van Veen
2021-01-05 14:42 ` [Galene] " Juliusz Chroboczek
2021-01-05 14:52 ` Toke Høiland-Jørgensen
2021-01-05 18:16 ` Jeroen van Veen
2021-01-05 18:44 ` Michael Ströder
2021-01-05 21:49 ` Toke Høiland-Jørgensen
2021-01-08 13:19 ` Juliusz Chroboczek
2021-01-08 14:24 ` Michael Ströder [this message]
2021-01-08 14:58 ` Juliusz Chroboczek
2021-01-08 16:03 ` Michael Ströder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e189df9b-0599-9f62-c7a6-fd634b0e27db@stroeder.com \
--to=michael@stroeder.com \
--cc=galene@lists.galene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox