From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] rc-httpd bug
Date: Tue, 10 Feb 2015 15:19:20 +0000 [thread overview]
Message-ID: <20150210151920.Horde.WV9olLwU5stsc_byViLgDg6@ssl.eumx.net> (raw)
In-Reply-To: <73291f3a355aa90691520abe7aea1308@utsuho.znet>
Quoting BurnZeZ@feline.systems:
> Regardless of what lachs0r says, it's probably not the best idea to let
> your system be run out of memory serving http.
It's not even a good idea to serve http in the first place. It's amazing
eekee was able to even produce a working httpd in shell; getting fiddly with
tyring to harden a daemon which is obviously not intended to base your
business around is probably a waste of time.
Resource exhaustion problems are not easily fixed; see the recent 9fans
thread on the topic. In this case it would be simplest to write a small
utility to handle the ingest and drop the read operation after n bytes.
Patches welcome.
khm
prev parent reply other threads:[~2015-02-10 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 8:15 BurnZeZ
2015-02-09 14:55 ` [9front] " Kurt H Maier
2015-02-10 13:35 ` BurnZeZ
2015-02-10 15:19 ` Kurt H Maier [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=20150210151920.Horde.WV9olLwU5stsc_byViLgDg6@ssl.eumx.net \
--to=khm@sciops.net \
--cc=9front@9front.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.
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 NNTP newsgroup(s).