From: Eric Wong <e@80x24.org>
To: Lawrence Pit <lawrence.pit@gmail.com>
Cc: unicorn-public@bogomips.org
Subject: Re: unicorn log attack?
Date: Mon, 1 Feb 2016 09:57:57 +0000 [thread overview]
Message-ID: <20160201095757.GA14049@dcvr.yhbt.net> (raw)
In-Reply-To: <CAGHrWsiqS486dqLPw9mZiooLXk2yso-JEtnr1vM02HeP+f_2Ug@mail.gmail.com>
Lawrence Pit <lawrence.pit@gmail.com> wrote:
> Hi Eric,
>
> > but that includes emails :)
>
> Yeah, sorry about the email format :[ Hope this time it's as expected.
Yep, you can check for deliverability of any message by
checking: bogomips.org/unicorn-public/$MESSAGE_ID/
(or just look near the top of http://bogomips.org/unicorn-public/)
Nothing hits the list until it hits the archives.
I also suggest always Bcc:-ing yourself instead of having your
mail client save to a "Sent" folder so you can:
a) test deliverability (including the Message-ID: in headers
if it's added by the server and not your client)
b) get proper threading with any reply-to-all lists you're not
subscribed to.
> > I don't consider it the responsibility of the app server to sanitize it.
>
> fwiw, I agree :) ... similarly, why consider it the responsibility of
> the app server to log it? it is an application level error, not a
> unicorn error.
I'm not entirely sure why unicorn logs it, either. I think it
was already expected in 2009 for application servers to log
that (thin/mongrel/...?)
Similarly, I don't like the "timeout" feature of unicorn
anymore, either since it encourages hiding bugs.
There's no chance of removing either feature, of course.
prev parent reply other threads:[~2016-02-01 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56AAAD0A.8000807@icloud.com>
2016-01-30 9:34 ` unicorn log attack? Eric Wong
2016-02-01 5:04 ` Lawrence Pit
2016-02-01 9:57 ` Eric Wong [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://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160201095757.GA14049@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=lawrence.pit@gmail.com \
--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).