From: Eric Wong <e@80x24.org>
To: unicorn-public@bogomips.org
Subject: possible errors reading mailing list archives
Date: Tue, 7 Apr 2015 23:22:18 +0000 [thread overview]
Message-ID: <20150407232218.GA8875@dcvr.yhbt.net> (raw)
If you hit any errors or truncated/corrupted responses when reading ML
archives at http://bogomips.org/unicorn-public/ it's probably because of
a bug in the new rack.hijack-based proxy in front of the prefork Apache2
instance hosting.
Drop me (or this list) a plain-text mail with the URL(s) and any info
about your client/connection that's broken for you
Previously, it was yahns using a synchronous (Rack, no-hijack) proxy
from yahns in the extras/proxy_pass.rb file[2]
before:
yahns:extras/proxy_pass.rb -> varnish -> mpm_prefork+mod_perl
after:
yahns:lib/yahns/proxy_pass.rb -> varnish -> mpm_prefork+mod_perl
yahns mailing list archives with all the relevant commits are here:
http://yhbt.net/yahns-public/
In case the HTTP portion of the archives get hosed, archives of the
mailing lists are still git clonable with ssoma[1] (or just using
"git clone")
git://yhbt.net/yahns-public
git://bogomips.org/unicorn-public
In case the server is gets completely hosed by the yahns proxy_pass
changes, archives are still readable at:
https://www.mail-archive.com/yahns-public@yhbt.net/
https://www.mail-archive.com/unicorn-public@bogomips.org/
Finally, in case you haven't realized by now; unicorn has always been a
rip-off of Apache(1|2) prefork design. The major difference is the
marketing of unicorn always focused on the shortcomings of the design :>
So any fully-buffering reverse proxy such as nginx or yahns/proxy_pass
which protects one preforking server implementation from slow clients
will protect another...
[1] http://ssoma.public-inbox.org/
[2] git clone git://yhbt.net/yahns
reply other threads:[~2015-04-07 23:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150407232218.GA8875@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=unicorn-public@bogomips.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
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).