all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 38411@debbugs.gnu.org
Subject: bug#38411: closed (HTTP pipelining of narinfo requests broken for https://ci.guix.gnu.org)
Date: Thu, 26 Dec 2019 19:14:28 +0100	[thread overview]
Message-ID: <87sgl7gdiz.fsf@gnu.org> (raw)
In-Reply-To: <handler.38411.D38411.157729267617189.notifdone@debbugs.gnu.org> (GNU bug Tracking System's message of "Wed, 25 Dec 2019 16:52:02 +0000")

Hi Gábor,

help-debbugs@gnu.org (GNU bug Tracking System) skribis:

> This was an upstream regression introduced in nginx 1.17.5.
> It is fixed in 1.17.7. Fixed by updating nginx to 1.17.7 in commit:
> 32dfde905229e593f9fe60795d2490f99c27aad5
> and updating berlin config in maintenance on commit:
> 87d451e9c3381b21e6c7208372576abed84df1e6.
>
> This is mentioned on then nginx 1.17.7 release notes as:
>
> Bugfix: a timeout might occur while handling pipelined requests in an
> SSL connection; the bug had appeared in 1.17.5.

I’m really happy you were able to pinpoint the issue and to help
upstream diagnose it.  The power of free software!

Thank you,
Ludo’.

      parent reply	other threads:[~2019-12-26 18:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28  9:22 bug#38411: HTTP pipelining of narinfo requests broken for https://ci.guix.gnu.org Ludovic Courtès
2019-11-28  9:59 ` Ludovic Courtès
2019-11-28 10:18   ` Ludovic Courtès
2019-11-28 10:29   ` Ludovic Courtès
2019-11-28 10:04 ` Ludovic Courtès
2019-12-25 16:50 ` Gábor Boskovits
     [not found] ` <handler.38411.D38411.157729267617189.notifdone@debbugs.gnu.org>
2019-12-26 18:14   ` Ludovic Courtès [this message]

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=87sgl7gdiz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38411@debbugs.gnu.org \
    --cc=boskovits@gmail.com \
    /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.