From: Mathieu Othacehe <othacehe@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 48468@debbugs.gnu.org
Subject: bug#48468: substitute server connection timeout
Date: Mon, 17 May 2021 16:49:49 +0200 [thread overview]
Message-ID: <87eee59zzm.fsf@gnu.org> (raw)
In-Reply-To: <87eee6cz75.fsf@cbaines.net> (Christopher Baines's message of "Sun, 16 May 2021 19:26:22 +0100")
Hey,
> That's on the server side, the actual problem is probably on the client
> side, as I guess there are possibly places where closed connections
> aren't handled properly. This reminds me I sent some patches relating to
> closing connections, this could well be related [1].
Oh, you're right, the Nginx server probably makes the difference
here. The http-write procedure of the Guile (web server http) module
seems to handle keep-alive connections. However, the wrapping http-write
procedure of (guix scripts publish) may not.
I'll have a closer look, thanks for your help.
Mathieu
next prev parent reply other threads:[~2021-05-17 14:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 17:57 bug#48468: substitute server connection timeout Mathieu Othacehe
2021-05-16 18:26 ` Christopher Baines
2021-05-17 14:49 ` Mathieu Othacehe [this message]
2021-05-18 14:35 ` Mathieu Othacehe
2021-05-21 13:30 ` Mathieu Othacehe
2021-05-29 21:44 ` Ludovic Courtès
2021-06-18 12:33 ` Ludovic Courtès
2021-06-29 16:49 ` Mathieu Othacehe
2022-12-05 13:21 ` Ludovic Courtès
2022-12-07 9:44 ` Mathieu Othacehe
2022-12-07 13:38 ` Ludovic Courtès
2022-12-07 14:31 ` Mathieu Othacehe
2022-12-08 10:26 ` Ludovic Courtès
2022-12-10 10:55 ` Ludovic Courtès
2022-12-27 9:52 ` Mathieu Othacehe
2022-12-28 14:23 ` Mathieu Othacehe
2023-01-06 22:42 ` Ludovic Courtès
2023-01-07 13:40 ` Mathieu Othacehe
2023-01-09 9:39 ` Ludovic Courtès
2023-01-10 8:10 ` Mathieu Othacehe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eee59zzm.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=48468@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.