From: Tobias Geerinckx-Rice <me@tobias.gr>
To: swedebugia <swedebugia@riseup.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Berlin substitute server "Bad Read-Header-Line header: #<eof>
Date: Mon, 05 Nov 2018 15:10:54 +0100 [thread overview]
Message-ID: <87a7mnobrl.fsf@nckx> (raw)
In-Reply-To: <fa300a0c-9f29-a186-2bc5-7edef477822f@riseup.net>
swedebugia (nomen est omen :-),
swedebugia wrote:
> On 2018-11-04 23:53, Ludovic Courtès wrote:
>> For the record, this was due to lack of disk space on that
>> machine > (nginx was unable to reply at all.)
> Could we catch cases like these and print a nice error instead
> of a
> backtrace?
>
> If you point me to the right line and file I could try writing a
> patch :D
I'll leave this[0] here in case it's the same 'bug'. The
*.http.response reproducers were nothing but a bunch of nohupped
netcats and no longer work.
If it is related, I could dig up & bang my half-finished patch
into shape & submit it.
If not, it might point you to the right area to start digging.
Kind regards,
T G-R
[0]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26489
prev parent reply other threads:[~2018-11-05 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 19:17 Berlin substitute server "Bad Read-Header-Line header: #<eof> Leo Famulari
2018-11-01 20:49 ` Tobias Geerinckx-Rice
2018-11-02 11:18 ` Giovanni Biscuolo
2018-11-04 22:53 ` Ludovic Courtès
2018-11-05 9:05 ` swedebugia
2018-11-05 14:10 ` Tobias Geerinckx-Rice [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7mnobrl.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=swedebugia@riseup.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).