From: "Ludovic Courtès" <ludo@gnu.org>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: 54171@debbugs.gnu.org
Subject: bug#54171: [PATCH] web: default to INADDR_ANY instead of INADDR_LOOPBACK
Date: Tue, 01 Mar 2022 09:49:15 +0100 [thread overview]
Message-ID: <87zgma83ck.fsf@gnu.org> (raw)
In-Reply-To: <20220226181132.64743-1-aconchillo@gmail.com> ("Aleix Conchillo Flaqué"'s message of "Sat, 26 Feb 2022 10:11:32 -0800")
Bon dia!
Aleix Conchillo Flaqué <aconchillo@gmail.com> skribis:
> Using INADDR_ANY instead of INADDR_LOOPBACK makes it convenient when
> starting the web server inside containers without the need to having to
> specify INADDR_ANY all the time. This is the default in most libraries
> and languages.
>
> This doesn't break backwards compatibility since INADDR_LOOPBACK is also
> included in INADDR_ANY.
A potential problem with changing the default is that people using the
defaults would all of a sudden have their servers accessible from the
outside, which could be a real problem.
Also, defaulting to INADDR_LOOPBACK is a conservative choice, with the
understanding that you have to explicitly say so if you want your server
to be directly accessible from the outside. (In most cases, one would
run Guile web servers behind a proxy such as nginx.)
So I have a preference for the status quo.
WDYT?
Ludo’.
prev parent reply other threads:[~2022-03-01 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 18:11 bug#54171: [PATCH] web: default to INADDR_ANY instead of INADDR_LOOPBACK Aleix Conchillo Flaqué
2022-03-01 8:49 ` 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgma83ck.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=54171@debbugs.gnu.org \
--cc=aconchillo@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.
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).